Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c9675dbf77b6f83a0e459a173ad585fa17ad940e4015d92a795cd0505385def

Tx prefix hash: cbc5a3f5a51e5615de6a7bde444ccd568d7379adbcf6b5ba6ca1898e9fcba4ea
Tx public key: 7e7c25666092baa4394ee1ff39848729077b4a5d4dbff5c5afb46b6bfc1750e3
Timestamp: 1723100570 Timestamp [UCT]: 2024-08-08 07:02:50 Age [y:d:h:m:s]: 00:253:03:11:29
Block: 1083257 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180817 RingCT/type: yes/0
Extra: 017e7c25666092baa4394ee1ff39848729077b4a5d4dbff5c5afb46b6bfc1750e3021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ff63c69140c5a890d70f78365e3c3e439c36906b3c5cb3de12d5f83d1d521a1 0.600000000000 1557110 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": 1083267, "vin": [ { "gen": { "height": 1083257 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ff63c69140c5a890d70f78365e3c3e439c36906b3c5cb3de12d5f83d1d521a1" } } ], "extra": [ 1, 126, 124, 37, 102, 96, 146, 186, 164, 57, 78, 225, 255, 57, 132, 135, 41, 7, 123, 74, 93, 77, 191, 245, 197, 175, 180, 107, 107, 252, 23, 80, 227, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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