Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8db4f956c9467b22c5624750d2fa7172b7667e0b491dcbc23d426979edd5e682

Tx prefix hash: 940f23bc4fdbc944f3ce5f8731d4b5ff633656e67d91a43da88cf67b4f68c61f
Tx public key: f3426c60d4c6596bd5467cd40ddbd67be4e554b2f0e903aa502ca21b25375bc6
Timestamp: 1663436557 Timestamp [UCT]: 2022-09-17 17:42:37 Age [y:d:h:m:s]: 02:077:02:16:55
Block: 590044 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 576602 RingCT/type: yes/0
Extra: 01f3426c60d4c6596bd5467cd40ddbd67be4e554b2f0e903aa502ca21b25375bc6021100000001faf35c9c000000000000000000

1 output(s) for total of 6.806743158000 dcy

stealth address amount amount idx
00: 31baa5ecf584a674e591cd6b4e4162295193c5bcd3e09938560eb6418e8382df 6.806743158000 1024423 of 0

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": 590054, "vin": [ { "gen": { "height": 590044 } } ], "vout": [ { "amount": 6806743158, "target": { "key": "31baa5ecf584a674e591cd6b4e4162295193c5bcd3e09938560eb6418e8382df" } } ], "extra": [ 1, 243, 66, 108, 96, 212, 198, 89, 107, 213, 70, 124, 212, 13, 219, 214, 123, 228, 229, 84, 178, 240, 233, 3, 170, 80, 44, 162, 27, 37, 55, 91, 198, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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