Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1a6b827c848816fe027db076ce60cabdfc68c8222866de893e15dd98dc439e9

Tx prefix hash: b71e40b9507da7ef278a21ec48216c1abefdbff38a421515443828ff4a6fefd4
Tx public key: eebf609d655f741a91c0e75f4e233b097b3af5d1fbc03577f1b8276a027ee748
Timestamp: 1728908511 Timestamp [UCT]: 2024-10-14 12:21:51 Age [y:d:h:m:s]: 00:002:11:15:31
Block: 1131412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1771 RingCT/type: yes/0
Extra: 01eebf609d655f741a91c0e75f4e233b097b3af5d1fbc03577f1b8276a027ee748021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d54655f6dc9d80941a7d73d7d0c8272c5df1e713908754d3ec0aeda6b5b26355 0.600000000000 1614311 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": 1131422, "vin": [ { "gen": { "height": 1131412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d54655f6dc9d80941a7d73d7d0c8272c5df1e713908754d3ec0aeda6b5b26355" } } ], "extra": [ 1, 238, 191, 96, 157, 101, 95, 116, 26, 145, 192, 231, 95, 78, 35, 59, 9, 123, 58, 245, 209, 251, 192, 53, 119, 241, 184, 39, 106, 2, 126, 231, 72, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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