Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17f30b50719ef68972aaa37e4e91fa3ef865fa500d257e70daaa31c2f3514c18

Tx prefix hash: 8178085a8d3fe9599acca8c1b312d27fb9d296145c8ae725f493d238928c827a
Tx public key: be74328197f8021b8f1354b6b15d52e0474a8134a08982b6fe3398a50e0c5bc3
Timestamp: 1709121474 Timestamp [UCT]: 2024-02-28 11:57:54 Age [y:d:h:m:s]: 01:298:04:17:46
Block: 967374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 471883 RingCT/type: yes/0
Extra: 01be74328197f8021b8f1354b6b15d52e0474a8134a08982b6fe3398a50e0c5bc30211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4207b907b95d51ab6cba2abf6ed36953da86c7a351a07e68d23448f23ae4ec71 0.600000000000 1427151 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": 967384, "vin": [ { "gen": { "height": 967374 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4207b907b95d51ab6cba2abf6ed36953da86c7a351a07e68d23448f23ae4ec71" } } ], "extra": [ 1, 190, 116, 50, 129, 151, 248, 2, 27, 143, 19, 84, 182, 177, 93, 82, 224, 71, 74, 129, 52, 160, 137, 130, 182, 254, 51, 152, 165, 14, 12, 91, 195, 2, 17, 0, 0, 0, 2, 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