Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f250b8b59f931efedaa72f5bdd30a5aa870dd38b17cdf7e36e3f8d147509bc6f

Tx prefix hash: 4d5968a7868649813f22f454879370e445e44def60dd3b52495acd6c4de3c0d5
Tx public key: d807800a34020eee0d3cabb5b351e8ddf30ce964ae79b55640e2c3d5d194beae
Timestamp: 1656651725 Timestamp [UCT]: 2022-07-01 05:02:05 Age [y:d:h:m:s]: 03:123:01:26:22
Block: 534083 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 867670 RingCT/type: yes/0
Extra: 01d807800a34020eee0d3cabb5b351e8ddf30ce964ae79b55640e2c3d5d194beae0211000000015eb576c5000000000000000000

1 output(s) for total of 10.431853231000 dcy

stealth address amount amount idx
00: 84d402e31bf33c5e25dcfab0d0b8b4c7d0d1abf536d06b7ea6d2a823349c4ea8 10.431853231000 963490 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": 534093, "vin": [ { "gen": { "height": 534083 } } ], "vout": [ { "amount": 10431853231, "target": { "key": "84d402e31bf33c5e25dcfab0d0b8b4c7d0d1abf536d06b7ea6d2a823349c4ea8" } } ], "extra": [ 1, 216, 7, 128, 10, 52, 2, 14, 238, 13, 60, 171, 181, 179, 81, 232, 221, 243, 12, 233, 100, 174, 121, 181, 86, 64, 226, 195, 213, 209, 148, 190, 174, 2, 17, 0, 0, 0, 1, 94, 181, 118, 197, 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