Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d265f3aabd2e86b4e3982831f526f617a9f4f03b4b32dd30b535e6389042740

Tx prefix hash: 163cd559d5c08df849645b3ab4e015b90988b9e54aaca59cb6ee2b29e84d23f3
Tx public key: e744f35b05b1e56844cce14b8f4a6dad57b344c4cc1e3ed6c178abed60180d2d
Timestamp: 1737009747 Timestamp [UCT]: 2025-01-16 06:42:27 Age [y:d:h:m:s]: 00:334:06:13:35
Block: 1198421 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236444 RingCT/type: yes/0
Extra: 01e744f35b05b1e56844cce14b8f4a6dad57b344c4cc1e3ed6c178abed60180d2d021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12f14fca670be2eeb5af2e793460c92bc57e0fa06e6ecdec6ca88b27a1e5d943 0.600000000000 1685046 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": 1198431, "vin": [ { "gen": { "height": 1198421 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12f14fca670be2eeb5af2e793460c92bc57e0fa06e6ecdec6ca88b27a1e5d943" } } ], "extra": [ 1, 231, 68, 243, 91, 5, 177, 229, 104, 68, 204, 225, 75, 143, 74, 109, 173, 87, 179, 68, 196, 204, 30, 62, 214, 193, 120, 171, 237, 96, 24, 13, 45, 2, 17, 0, 0, 0, 1, 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