Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ca9ad985c36d0dbc1f425667b6778c11faef898d8a80177e6880c46eb770fa4

Tx prefix hash: 191a84eac9112aeaa34e28ed27d6958f177678b7e91c1de3173c67753fbb59de
Tx public key: c8c919ec4ae9d1d315751f13a7f48321c2f0e6cf563e5d76298838d104301c5d
Timestamp: 1733574803 Timestamp [UCT]: 2024-12-07 12:33:23 Age [y:d:h:m:s]: 00:111:01:07:06
Block: 1169989 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79165 RingCT/type: yes/0
Extra: 01c8c919ec4ae9d1d315751f13a7f48321c2f0e6cf563e5d76298838d104301c5d021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f580de084c8bff048f8aa1bf071190d741059a11abbf24c0ed15734d243cadfd 0.600000000000 1655716 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": 1169999, "vin": [ { "gen": { "height": 1169989 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f580de084c8bff048f8aa1bf071190d741059a11abbf24c0ed15734d243cadfd" } } ], "extra": [ 1, 200, 201, 25, 236, 74, 233, 209, 211, 21, 117, 31, 19, 167, 244, 131, 33, 194, 240, 230, 207, 86, 62, 93, 118, 41, 136, 56, 209, 4, 48, 28, 93, 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