Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0b02a686e90c0d6511feaf9eaf7a2d575d2518a95667a2d4ae131640394fd0a

Tx prefix hash: e5a392cd9a9eac4c37794be65c1d72f183768cd708ddedfbd49cb215b203e8f9
Tx public key: 271d5a3e81c77393dce3490062efee9fe6f6291f9ed1d28c5bf57365b567c551
Timestamp: 1703201712 Timestamp [UCT]: 2023-12-21 23:35:12 Age [y:d:h:m:s]: 02:041:06:02:11
Block: 918285 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 549113 RingCT/type: yes/0
Extra: 01271d5a3e81c77393dce3490062efee9fe6f6291f9ed1d28c5bf57365b567c5510211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 527e9aba2c8f5970dd7ea3546ac49021ff808ae84d6bbee89f2417dc9c40834c 0.600000000000 1375927 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": 918295, "vin": [ { "gen": { "height": 918285 } } ], "vout": [ { "amount": 600000000, "target": { "key": "527e9aba2c8f5970dd7ea3546ac49021ff808ae84d6bbee89f2417dc9c40834c" } } ], "extra": [ 1, 39, 29, 90, 62, 129, 199, 115, 147, 220, 227, 73, 0, 98, 239, 238, 159, 230, 246, 41, 31, 158, 209, 210, 140, 91, 245, 115, 101, 181, 103, 197, 81, 2, 17, 0, 0, 0, 3, 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