Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74df9326e65de79c6a240bcb90281fa82068f6174d1db1390d3e60f9bbffc3b3

Tx prefix hash: 1a01001e311cbc790874cc8d1ca52a312c5426beacccfe336bba63355bebd28d
Tx public key: 89c1b5f819ddd2d706fc1eaea158195b7a244442a6e12d4a7a9275dd2bb1bf4e
Timestamp: 1577567427 Timestamp [UCT]: 2019-12-28 21:10:27 Age [y:d:h:m:s]: 05:307:16:04:12
Block: 33840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1367391 RingCT/type: yes/0
Extra: 0189c1b5f819ddd2d706fc1eaea158195b7a244442a6e12d4a7a9275dd2bb1bf4e0211000000109159db1e000000000000000000

1 output(s) for total of 474.161905918000 dcy

stealth address amount amount idx
00: ba8507257e9269b3e68aff26c7f86ada48b5c57657b73da2c4aa2434143731fd 474.161905918000 56784 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": 33850, "vin": [ { "gen": { "height": 33840 } } ], "vout": [ { "amount": 474161905918, "target": { "key": "ba8507257e9269b3e68aff26c7f86ada48b5c57657b73da2c4aa2434143731fd" } } ], "extra": [ 1, 137, 193, 181, 248, 25, 221, 210, 215, 6, 252, 30, 174, 161, 88, 25, 91, 122, 36, 68, 66, 166, 225, 45, 74, 122, 146, 117, 221, 43, 177, 191, 78, 2, 17, 0, 0, 0, 16, 145, 89, 219, 30, 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