Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7bccd8c21dde584e3f81d458dc1f5c63ea4defa63e387a8d40284f8dd7ec196b

Tx prefix hash: 537c899c5eb0747e89d233bb4e954c1b4827d06636f5e8c59f04aa8883aae9ec
Tx public key: cdfe699124843ea46b5530a42552f93909f37b31e4f675f7c1f353d4a984c80b
Timestamp: 1698420694 Timestamp [UCT]: 2023-10-27 15:31:34 Age [y:d:h:m:s]: 01:076:18:58:46
Block: 878869 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316094 RingCT/type: yes/0
Extra: 01cdfe699124843ea46b5530a42552f93909f37b31e4f675f7c1f353d4a984c80b021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.751522836000 dcy

stealth address amount amount idx
00: 650532c43d567f8b73053e694eab9a3fb54c94fab92e04520ef6f922aaabdb4c 0.751522836000 1334359 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": 878879, "vin": [ { "gen": { "height": 878869 } } ], "vout": [ { "amount": 751522836, "target": { "key": "650532c43d567f8b73053e694eab9a3fb54c94fab92e04520ef6f922aaabdb4c" } } ], "extra": [ 1, 205, 254, 105, 145, 36, 132, 62, 164, 107, 85, 48, 164, 37, 82, 249, 57, 9, 243, 123, 49, 228, 246, 117, 247, 193, 243, 83, 212, 169, 132, 200, 11, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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