Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39076e2cf6c469b239152197e77bd60ba3fe2c485acb22cd51366092b8dba26c

Tx prefix hash: d81753e8c996786bc4b5ecc6e8777689b0fdbf729e7dfd09a8305694d85d1589
Tx public key: 2fac07e72c16f1326043a855b277a08a5be2d7d680d09c86ed4e262edf967d0b
Timestamp: 1737532474 Timestamp [UCT]: 2025-01-22 07:54:34 Age [y:d:h:m:s]: 00:146:04:43:52
Block: 1202720 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104240 RingCT/type: yes/0
Extra: 012fac07e72c16f1326043a855b277a08a5be2d7d680d09c86ed4e262edf967d0b02110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a6b53726003de1bfb18e53d2c425a04ef1bfb599345dc5f4b0ae6b02a09d450 0.600000000000 1689385 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": 1202730, "vin": [ { "gen": { "height": 1202720 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a6b53726003de1bfb18e53d2c425a04ef1bfb599345dc5f4b0ae6b02a09d450" } } ], "extra": [ 1, 47, 172, 7, 231, 44, 22, 241, 50, 96, 67, 168, 85, 178, 119, 160, 138, 91, 226, 215, 214, 128, 208, 156, 134, 237, 78, 38, 46, 223, 150, 125, 11, 2, 17, 0, 0, 0, 10, 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