Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77215202781a791d8a49645b0fe724545d40e49926533700c1f1848fb37bf1f7

Tx prefix hash: ff1b9d0b900f8c9ee8476779b83ec40901f07888ea5f18b59c8da947ce0e4a2c
Tx public key: cc32a710cd5d97a6bc33cee6de3dec610d64d68087dbf5533862cba052e58145
Timestamp: 1733600488 Timestamp [UCT]: 2024-12-07 19:41:28 Age [y:d:h:m:s]: 00:114:13:56:03
Block: 1170212 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81671 RingCT/type: yes/0
Extra: 01cc32a710cd5d97a6bc33cee6de3dec610d64d68087dbf5533862cba052e581450211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00c0eb7d8bf7776f56355ecf95ed4d819d7e9c2bc9498d357e39c01b802a4bce 0.600000000000 1655941 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": 1170222, "vin": [ { "gen": { "height": 1170212 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00c0eb7d8bf7776f56355ecf95ed4d819d7e9c2bc9498d357e39c01b802a4bce" } } ], "extra": [ 1, 204, 50, 167, 16, 205, 93, 151, 166, 188, 51, 206, 230, 222, 61, 236, 97, 13, 100, 214, 128, 135, 219, 245, 83, 56, 98, 203, 160, 82, 229, 129, 69, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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