Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c40bcd97a4e5ac9ef45f3e59afdd58c3dc1cbe29c4827fa8bddbfcc179a8f87

Tx prefix hash: 23b0a205b2c90136453007b975b7d7489ba432cf8a6f4eafcb4c392edbfd0019
Tx public key: a6de00f9705b93e900f9f09dcf0c01500274d5d10b678253e430e95718795e63
Timestamp: 1740494849 Timestamp [UCT]: 2025-02-25 14:47:29 Age [y:d:h:m:s]: 00:268:21:15:02
Block: 1227000 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189934 RingCT/type: yes/0
Extra: 01a6de00f9705b93e900f9f09dcf0c01500274d5d10b678253e430e95718795e63021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4085b1afdaf8e9b3d4863b1334787af984413c41e993d001154dcd3e720f7706 0.600000000000 1713873 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": 1227010, "vin": [ { "gen": { "height": 1227000 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4085b1afdaf8e9b3d4863b1334787af984413c41e993d001154dcd3e720f7706" } } ], "extra": [ 1, 166, 222, 0, 249, 112, 91, 147, 233, 0, 249, 240, 157, 207, 12, 1, 80, 2, 116, 213, 209, 11, 103, 130, 83, 228, 48, 233, 87, 24, 121, 94, 99, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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