Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c0dc953e332ebeada3eff80839c1c02d759a4908985ce174e89e11c172c3959

Tx prefix hash: 2def68690969ff3ed5111121684f5c7b1eb86e18afdc7fa2ac61307be22065e6
Tx public key: 9c6c75301593ab7c2c6dcb4fb17ffb25e80cf6516df1b18e1b1e1b6ab4943455
Timestamp: 1734324589 Timestamp [UCT]: 2024-12-16 04:49:49 Age [y:d:h:m:s]: 00:025:17:59:09
Block: 1176223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18387 RingCT/type: yes/0
Extra: 019c6c75301593ab7c2c6dcb4fb17ffb25e80cf6516df1b18e1b1e1b6ab4943455021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8709c937945bee4fdb1ad1220b2cda5f838565f9fc22ffedc52214efdb7d5742 0.600000000000 1662554 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": 1176233, "vin": [ { "gen": { "height": 1176223 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8709c937945bee4fdb1ad1220b2cda5f838565f9fc22ffedc52214efdb7d5742" } } ], "extra": [ 1, 156, 108, 117, 48, 21, 147, 171, 124, 44, 109, 203, 79, 177, 127, 251, 37, 232, 12, 246, 81, 109, 241, 177, 142, 27, 30, 27, 106, 180, 148, 52, 85, 2, 17, 0, 0, 0, 2, 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