Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ccc476af2a881f756598bb5cb6cbe7ba742379eed2e5bfe1dc21538d1a8cc297

Tx prefix hash: 50f5dd5ba22f69e43d82f601314f76d50dfebd387c03e34a64c47de3fb0d446a
Tx public key: ebf61e6bd07177738c9d2abdd692b1a9dd2761eef73fafb61b024c85941421e2
Timestamp: 1702314823 Timestamp [UCT]: 2023-12-11 17:13:43 Age [y:d:h:m:s]: 01:156:11:28:24
Block: 910942 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372987 RingCT/type: yes/0
Extra: 01ebf61e6bd07177738c9d2abdd692b1a9dd2761eef73fafb61b024c85941421e2021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67e4615a93412f8aa01f1389dae38c9f0a7db27438f5c4632939b8110d795ada 0.600000000000 1368117 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": 910952, "vin": [ { "gen": { "height": 910942 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67e4615a93412f8aa01f1389dae38c9f0a7db27438f5c4632939b8110d795ada" } } ], "extra": [ 1, 235, 246, 30, 107, 208, 113, 119, 115, 140, 157, 42, 189, 214, 146, 177, 169, 221, 39, 97, 238, 247, 63, 175, 182, 27, 2, 76, 133, 148, 20, 33, 226, 2, 17, 0, 0, 0, 1, 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