Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de45a1fed7691c63d20dbf14bb1399a02302338b2d4c4546d8cc332ab72824d8

Tx prefix hash: cbe8f85610b0d75c33501c609f4b017d0e0f47c1a668453fdab858c1a33e7feb
Tx public key: 1cf9cae430129cac085d8249efb0b5bfcacc096b2ea2c09b8d7661d58e41f348
Timestamp: 1635358079 Timestamp [UCT]: 2021-10-27 18:07:59 Age [y:d:h:m:s]: 03:061:14:57:09
Block: 361695 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 822490 RingCT/type: yes/0
Extra: 011cf9cae430129cac085d8249efb0b5bfcacc096b2ea2c09b8d7661d58e41f348021100000009328bb496000000000000000000

1 output(s) for total of 38.865326756000 dcy

stealth address amount amount idx
00: de74042715942006fe7f724f6a83527815d4176ce6d48866ab38e68325ad887d 38.865326756000 735765 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": 361705, "vin": [ { "gen": { "height": 361695 } } ], "vout": [ { "amount": 38865326756, "target": { "key": "de74042715942006fe7f724f6a83527815d4176ce6d48866ab38e68325ad887d" } } ], "extra": [ 1, 28, 249, 202, 228, 48, 18, 156, 172, 8, 93, 130, 73, 239, 176, 181, 191, 202, 204, 9, 107, 46, 162, 192, 155, 141, 118, 97, 213, 142, 65, 243, 72, 2, 17, 0, 0, 0, 9, 50, 139, 180, 150, 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