Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98bc8f0bf24bedb41e91e2ad979d6f3fe622d2a71337269488df7a8ad7b29e81

Tx prefix hash: 3fca71be668c9f9c9ce181eec917f52aa4479ea7146ab9f11a524c1b6851f400
Tx public key: c9d4e5b64565d0112c50fa4555c75a9bc4e2bfd0bcc1f62f0761b5df8805b4b0
Timestamp: 1717195173 Timestamp [UCT]: 2024-05-31 22:39:33 Age [y:d:h:m:s]: 00:289:13:34:36
Block: 1034303 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206962 RingCT/type: yes/0
Extra: 01c9d4e5b64565d0112c50fa4555c75a9bc4e2bfd0bcc1f62f0761b5df8805b4b002110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf81ea9d9020b58fc2227f3ead1705dc124f91f04c64f7146cc2d4b1cad14cad 0.600000000000 1502804 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": 1034313, "vin": [ { "gen": { "height": 1034303 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf81ea9d9020b58fc2227f3ead1705dc124f91f04c64f7146cc2d4b1cad14cad" } } ], "extra": [ 1, 201, 212, 229, 182, 69, 101, 208, 17, 44, 80, 250, 69, 85, 199, 90, 155, 196, 226, 191, 208, 188, 193, 246, 47, 7, 97, 181, 223, 136, 5, 180, 176, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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