Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ded77a73badc22e4c1860900aa6b8f1fa6e0233b1af3a824cba21c028c6030fb

Tx prefix hash: 82edf196ddd03266e2c87759c335005d3fed28ea7550a66f1c5a58288b344eba
Tx public key: 994abb07f21796df19ccd6f1610528b2c082d4fe2099fd104fe5824920e41acd
Timestamp: 1705850664 Timestamp [UCT]: 2024-01-21 15:24:24 Age [y:d:h:m:s]: 01:316:09:54:04
Block: 940218 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485003 RingCT/type: yes/0
Extra: 01994abb07f21796df19ccd6f1610528b2c082d4fe2099fd104fe5824920e41acd02110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 622bc5eca6f14c17a122810801c151d7593d115e04c51e75c60aa50d5164c74a 0.600000000000 1398352 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": 940228, "vin": [ { "gen": { "height": 940218 } } ], "vout": [ { "amount": 600000000, "target": { "key": "622bc5eca6f14c17a122810801c151d7593d115e04c51e75c60aa50d5164c74a" } } ], "extra": [ 1, 153, 74, 187, 7, 242, 23, 150, 223, 25, 204, 214, 241, 97, 5, 40, 178, 192, 130, 212, 254, 32, 153, 253, 16, 79, 229, 130, 73, 32, 228, 26, 205, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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