Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08e16b035c303738212b126ace8dceaa2459b90be1d7de6b67e00d9bf13b966f

Tx prefix hash: 89232455758eaf5ca4e097a6608f88c3961e821f064854786f9dcfba313e899d
Tx public key: 6e02a3157288726ccf3d67cd01f1eab9effbd37027507bec2d187e4697c2b933
Timestamp: 1700933761 Timestamp [UCT]: 2023-11-25 17:36:01 Age [y:d:h:m:s]: 01:171:02:11:05
Block: 899485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383478 RingCT/type: yes/0
Extra: 016e02a3157288726ccf3d67cd01f1eab9effbd37027507bec2d187e4697c2b93302110000000375e3f0e9000000000000000000

1 output(s) for total of 0.642144527000 dcy

stealth address amount amount idx
00: 2befb90f4c8c47bce3a541f641e2b5e8cef21611871a7c15043b0a1d66c7224c 0.642144527000 1355940 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": 899495, "vin": [ { "gen": { "height": 899485 } } ], "vout": [ { "amount": 642144527, "target": { "key": "2befb90f4c8c47bce3a541f641e2b5e8cef21611871a7c15043b0a1d66c7224c" } } ], "extra": [ 1, 110, 2, 163, 21, 114, 136, 114, 108, 207, 61, 103, 205, 1, 241, 234, 185, 239, 251, 211, 112, 39, 80, 123, 236, 45, 24, 126, 70, 151, 194, 185, 51, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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