Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b71c66b14133b4fdfb7883a817c4ef00097c51bed2551dc6d510fbeb8eb69127

Tx prefix hash: 840d5e3d6c13f6c9ed4a2089a901d6bac488aea20dc1026028333eb7ddd5edc3
Tx public key: 7514bb10710e41f589b4e00a682baeb3bfdf63d4bb8623d6730048e917e1d44f
Timestamp: 1702064526 Timestamp [UCT]: 2023-12-08 19:42:06 Age [y:d:h:m:s]: 01:050:09:40:24
Block: 908858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297160 RingCT/type: yes/0
Extra: 017514bb10710e41f589b4e00a682baeb3bfdf63d4bb8623d6730048e917e1d44f02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02dfa538f344c43e21ca4cf370c15f8f2c4853362a327c60f6b4bb59cdb4bd49 0.600000000000 1365915 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": 908868, "vin": [ { "gen": { "height": 908858 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02dfa538f344c43e21ca4cf370c15f8f2c4853362a327c60f6b4bb59cdb4bd49" } } ], "extra": [ 1, 117, 20, 187, 16, 113, 14, 65, 245, 137, 180, 224, 10, 104, 43, 174, 179, 191, 223, 99, 212, 187, 134, 35, 214, 115, 0, 72, 233, 23, 225, 212, 79, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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