Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5cc0d7ed17a6cb1c69632445c82d24a63f80bbb27017acb43dd98377d622ce2b

Tx prefix hash: 30a98583ada1ec05a71170345793932caf1343bd9920a51fc6b284226d9474f7
Tx public key: a69e1c4df947d7400a27af925f723a73b1475fd472eab7ccfad7ff83079377d3
Timestamp: 1698422606 Timestamp [UCT]: 2023-10-27 16:03:26 Age [y:d:h:m:s]: 01:233:15:30:56
Block: 878889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 427912 RingCT/type: yes/0
Extra: 01a69e1c4df947d7400a27af925f723a73b1475fd472eab7ccfad7ff83079377d30211000000024b8f5122000000000000000000

1 output(s) for total of 0.751408171000 dcy

stealth address amount amount idx
00: 2bc618604ede0f0dbc027d63fe87182b4d820334100a1ace43ef350616d5d419 0.751408171000 1334381 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": 878899, "vin": [ { "gen": { "height": 878889 } } ], "vout": [ { "amount": 751408171, "target": { "key": "2bc618604ede0f0dbc027d63fe87182b4d820334100a1ace43ef350616d5d419" } } ], "extra": [ 1, 166, 158, 28, 77, 249, 71, 215, 64, 10, 39, 175, 146, 95, 114, 58, 115, 177, 71, 95, 212, 114, 234, 183, 204, 250, 215, 255, 131, 7, 147, 119, 211, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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