Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74eb7435210be88d30468fcbce5765dda6c6654bac6b735281f181c3453783fb

Tx prefix hash: bfbe07f42ec341361a88b18142c6a4745b5c2de9f3dcaaa38b0310b8072e79ca
Tx public key: b976ecb229d81dafbca5aa5cd39b62f06a2a4e0589066fc96ab7a0f7d25fd1bf
Timestamp: 1717637720 Timestamp [UCT]: 2024-06-06 01:35:20 Age [y:d:h:m:s]: 00:298:17:34:27
Block: 1037966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213497 RingCT/type: yes/0
Extra: 01b976ecb229d81dafbca5aa5cd39b62f06a2a4e0589066fc96ab7a0f7d25fd1bf0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2ac51ffb001cf7160efa7870dc3e3107113270701b27347f6c1edacfbc1b0e5 0.600000000000 1506525 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": 1037976, "vin": [ { "gen": { "height": 1037966 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2ac51ffb001cf7160efa7870dc3e3107113270701b27347f6c1edacfbc1b0e5" } } ], "extra": [ 1, 185, 118, 236, 178, 41, 216, 29, 175, 188, 165, 170, 92, 211, 155, 98, 240, 106, 42, 78, 5, 137, 6, 111, 201, 106, 183, 160, 247, 210, 95, 209, 191, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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