Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 700bc528c49173c88ffd0f76cdb27d86575dbcbf59b23730b1c8e4a918823708

Tx prefix hash: 80f82c3853df36c2a0d80d766783fd0485df9850804a627f9f35bc59d72cd341
Tx public key: 47f4e405f820b87b9fc3059327cdb463bd79b5018c352478fdf05d767f901e3d
Timestamp: 1714465354 Timestamp [UCT]: 2024-04-30 08:22:34 Age [y:d:h:m:s]: 00:344:20:05:15
Block: 1011661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246515 RingCT/type: yes/0
Extra: 0147f4e405f820b87b9fc3059327cdb463bd79b5018c352478fdf05d767f901e3d02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7acb3b768e4ed062524a21d2e1ae2411c875cce8c7754f8abf509444e86ac7a 0.600000000000 1473947 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": 1011671, "vin": [ { "gen": { "height": 1011661 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7acb3b768e4ed062524a21d2e1ae2411c875cce8c7754f8abf509444e86ac7a" } } ], "extra": [ 1, 71, 244, 228, 5, 248, 32, 184, 123, 159, 195, 5, 147, 39, 205, 180, 99, 189, 121, 181, 1, 140, 53, 36, 120, 253, 240, 93, 118, 127, 144, 30, 61, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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