Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ac932ad141935da999dcfbf93ecd70b6a866d75b84a254cd45826da226a66af

Tx prefix hash: 60442c80719b5604cb277e11d227b26c662b8654721b1731e178248947473baf
Tx public key: f3eaf4c16e753c7a0e77703bed502b128f6456fc8601c6d2bf8a90d6a6a1dda8
Timestamp: 1733095417 Timestamp [UCT]: 2024-12-01 23:23:37 Age [y:d:h:m:s]: 00:128:05:13:05
Block: 1166023 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91435 RingCT/type: yes/0
Extra: 01f3eaf4c16e753c7a0e77703bed502b128f6456fc8601c6d2bf8a90d6a6a1dda802110000000c007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 956a773bd245fd46afa3aa08bb1bb3f02c1257990837ec7e06eea696634a1e06 0.600000000000 1651700 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": 1166033, "vin": [ { "gen": { "height": 1166023 } } ], "vout": [ { "amount": 600000000, "target": { "key": "956a773bd245fd46afa3aa08bb1bb3f02c1257990837ec7e06eea696634a1e06" } } ], "extra": [ 1, 243, 234, 244, 193, 110, 117, 60, 122, 14, 119, 112, 59, 237, 80, 43, 18, 143, 100, 86, 252, 134, 1, 198, 210, 191, 138, 144, 214, 166, 161, 221, 168, 2, 17, 0, 0, 0, 12, 0, 127, 151, 138, 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