Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b5715266256787563f0cf91a7ff4cf62fe8689049c90d7f28bca032aff9e182

Tx prefix hash: 2155ad9acca1235b65421d97f124b27544d0b105342dcd7f6016f20257bed41a
Tx public key: a62e343362928bdee59e4f4ef669e566f4d1f7a4872e1f05c7d3d4a71ca33ded
Timestamp: 1715381288 Timestamp [UCT]: 2024-05-10 22:48:08 Age [y:d:h:m:s]: 00:333:05:36:45
Block: 1019278 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238176 RingCT/type: yes/0
Extra: 01a62e343362928bdee59e4f4ef669e566f4d1f7a4872e1f05c7d3d4a71ca33ded02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79ac9351425b5e9d4947fd0e368974bd5bf820f1d00e8f3beaddc3a27f652255 0.600000000000 1483203 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": 1019288, "vin": [ { "gen": { "height": 1019278 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79ac9351425b5e9d4947fd0e368974bd5bf820f1d00e8f3beaddc3a27f652255" } } ], "extra": [ 1, 166, 46, 52, 51, 98, 146, 139, 222, 229, 158, 79, 78, 246, 105, 229, 102, 244, 209, 247, 164, 135, 46, 31, 5, 199, 211, 212, 167, 28, 163, 61, 237, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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