Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: fe70f503f7185df2c891a4e6c82484516474dd6ae411b193d60da9e18badb0fb

Tx prefix hash: d58a480df52bd6108e7b731e3b84e0a8938d7b07d2cb36819778d4576b0c8e1b
Tx public key: 8fdf14b2041bf0f989d356948c00fba1e54ac1b2d0759c90512a6c8ab02e292b
Timestamp: 1712632336 Timestamp [UCT]: 2024-04-09 03:12:16 Age [y:d:h:m:s]: 01:063:17:47:13
Block: 996444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306554 RingCT/type: yes/0
Extra: 018fdf14b2041bf0f989d356948c00fba1e54ac1b2d0759c90512a6c8ab02e292b021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d656f1f5d7ee8fe0ff3d9e924cc06ea54d55212f9caf9e2f34573d25010859c7 0.600000000000 1456862 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 996454, "vin": [ { "gen": { "height": 996444 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d656f1f5d7ee8fe0ff3d9e924cc06ea54d55212f9caf9e2f34573d25010859c7" } } ], "extra": [ 1, 143, 223, 20, 178, 4, 27, 240, 249, 137, 211, 86, 148, 140, 0, 251, 161, 229, 74, 193, 178, 208, 117, 156, 144, 81, 42, 108, 138, 176, 46, 41, 43, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8