Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab000dff7be8df8c14677019f3cbd792977713b457d0650bc72b3dc4e619cf7b

Tx prefix hash: ec0c66822daff34a56ed18f48bcd1101c242e33d5610d67f1182945d9a4ade56
Tx public key: 0c09c443e7d5e7b6a0733c02dac977fc8a6613370d493a2f216f59edcf307a65
Timestamp: 1723359476 Timestamp [UCT]: 2024-08-11 06:57:56 Age [y:d:h:m:s]: 00:238:21:47:21
Block: 1085407 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170618 RingCT/type: yes/0
Extra: 010c09c443e7d5e7b6a0733c02dac977fc8a6613370d493a2f216f59edcf307a65021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 807ddbf68fb409c50c646cad0f9d30c5df0deb285e4bfffbe67997dc0ddb78ec 0.600000000000 1559984 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": 1085417, "vin": [ { "gen": { "height": 1085407 } } ], "vout": [ { "amount": 600000000, "target": { "key": "807ddbf68fb409c50c646cad0f9d30c5df0deb285e4bfffbe67997dc0ddb78ec" } } ], "extra": [ 1, 12, 9, 196, 67, 231, 213, 231, 182, 160, 115, 60, 2, 218, 201, 119, 252, 138, 102, 19, 55, 13, 73, 58, 47, 33, 111, 89, 237, 207, 48, 122, 101, 2, 17, 0, 0, 0, 1, 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