Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27202df0d3e012cead6d435873af936e805b20490dad4ef99cd8d01f3fa1dde9

Tx prefix hash: 606640ccfc244ed377aba7ac44c370d911aa694b7306efa49328b2fd6d5af3e9
Tx public key: 12c3fceafe7112aae07794f392bcfbbfc14a56dfc5c5ff9e9530f83ea591432c
Timestamp: 1722627314 Timestamp [UCT]: 2024-08-02 19:35:14 Age [y:d:h:m:s]: 00:082:07:39:57
Block: 1079341 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58930 RingCT/type: yes/0
Extra: 0112c3fceafe7112aae07794f392bcfbbfc14a56dfc5c5ff9e9530f83ea591432c021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6a0fbacf9b3fee66cbb10dc68361e0e80c0b437a8590723f16f954a58c92d99 0.600000000000 1552254 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": 1079351, "vin": [ { "gen": { "height": 1079341 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6a0fbacf9b3fee66cbb10dc68361e0e80c0b437a8590723f16f954a58c92d99" } } ], "extra": [ 1, 18, 195, 252, 234, 254, 113, 18, 170, 224, 119, 148, 243, 146, 188, 251, 191, 193, 74, 86, 223, 197, 197, 255, 158, 149, 48, 248, 62, 165, 145, 67, 44, 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