Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3000dd5b2da472e66d009d877e3cb1d89a93def05b8f11ec762e0c009d4ea94

Tx prefix hash: 28d3106a6f6de506a13e093c9709b420752005e44f63705942521504ff750cfe
Tx public key: d100c6ed37a76d4e8083d28e1f92ba5ead48f5a4ff17ab62b752f695c4b1157a
Timestamp: 1710385831 Timestamp [UCT]: 2024-03-14 03:10:31 Age [y:d:h:m:s]: 00:306:23:39:39
Block: 977865 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219735 RingCT/type: yes/0
Extra: 01d100c6ed37a76d4e8083d28e1f92ba5ead48f5a4ff17ab62b752f695c4b1157a0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c43af2e4b68c4ec0807d02ef4581cb5cd5483e7165d4f899570a5e3fe3326274 0.600000000000 1437872 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": 977875, "vin": [ { "gen": { "height": 977865 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c43af2e4b68c4ec0807d02ef4581cb5cd5483e7165d4f899570a5e3fe3326274" } } ], "extra": [ 1, 209, 0, 198, 237, 55, 167, 109, 78, 128, 131, 210, 142, 31, 146, 186, 94, 173, 72, 245, 164, 255, 23, 171, 98, 183, 82, 246, 149, 196, 177, 21, 122, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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