Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5f84ad72b72a6708fe58e75a210f8ef4b73b9725519e2b543ed76af90383a4c

Tx prefix hash: e1be377f3636e947df813ed4fcc6d2c70a1430579229b50d023d12cd06ace555
Tx public key: 694c095b5133b17038e8f5d011c0c84dc0d01b12488179ea2e02baa7a29a7208
Timestamp: 1732452074 Timestamp [UCT]: 2024-11-24 12:41:14 Age [y:d:h:m:s]: 00:134:05:50:14
Block: 1160692 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95748 RingCT/type: yes/0
Extra: 01694c095b5133b17038e8f5d011c0c84dc0d01b12488179ea2e02baa7a29a7208021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa595d06462063529e646d5b5426b7f650ff5536326fdd5927c2c954fe6a19a0 0.600000000000 1646341 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": 1160702, "vin": [ { "gen": { "height": 1160692 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa595d06462063529e646d5b5426b7f650ff5536326fdd5927c2c954fe6a19a0" } } ], "extra": [ 1, 105, 76, 9, 91, 81, 51, 177, 112, 56, 232, 245, 208, 17, 192, 200, 77, 192, 208, 27, 18, 72, 129, 121, 234, 46, 2, 186, 167, 162, 154, 114, 8, 2, 17, 0, 0, 0, 1, 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