Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9c0a377ef107a4d7b5a30279e3adc8f46e0dcc32ad2067d573b1f78152a7f4e

Tx prefix hash: be07e909126b91a01097abb9fb6e19993413a6f5e3808973655d7c6872d1d2ca
Tx public key: d334e9aad7ce3d2075e63d490c9694fea6fe784a64f356ff0cf73dab5c1808fb
Timestamp: 1696201724 Timestamp [UCT]: 2023-10-01 23:08:44 Age [y:d:h:m:s]: 01:186:16:18:32
Block: 860452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394472 RingCT/type: yes/0
Extra: 01d334e9aad7ce3d2075e63d490c9694fea6fe784a64f356ff0cf73dab5c1808fb02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.864898960000 dcy

stealth address amount amount idx
00: 4aad3e4ea6d6fa8536fb359f9651f2b85972a7dfec7cd743a708942754965639 0.864898960000 1314738 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": 860462, "vin": [ { "gen": { "height": 860452 } } ], "vout": [ { "amount": 864898960, "target": { "key": "4aad3e4ea6d6fa8536fb359f9651f2b85972a7dfec7cd743a708942754965639" } } ], "extra": [ 1, 211, 52, 233, 170, 215, 206, 61, 32, 117, 230, 61, 73, 12, 150, 148, 254, 166, 254, 120, 74, 100, 243, 86, 255, 12, 247, 61, 171, 92, 24, 8, 251, 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