Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10d96204ec5efdea9e700ceb7a4417b474121a1314494e02c41b655a9d6363db

Tx prefix hash: c1011f5a39dc5ecbc3a12dd8b6eb08c13c283a168f697deb0f184328d43c2878
Tx public key: 409935e9aabec0b4b6e88d4fc5475474e1d4b03fb9f6216449ebd4743d7e71e0
Timestamp: 1696339912 Timestamp [UCT]: 2023-10-03 13:31:52 Age [y:d:h:m:s]: 01:178:18:43:00
Block: 861600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388816 RingCT/type: yes/0
Extra: 01409935e9aabec0b4b6e88d4fc5475474e1d4b03fb9f6216449ebd4743d7e71e002110000000433af99f4000000000000000000

1 output(s) for total of 0.857356752000 dcy

stealth address amount amount idx
00: 4c4f388a5bfc749ab80cf334a71ba8730e2bcd237a5299e391af6639657eee97 0.857356752000 1315954 of 0

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": 861610, "vin": [ { "gen": { "height": 861600 } } ], "vout": [ { "amount": 857356752, "target": { "key": "4c4f388a5bfc749ab80cf334a71ba8730e2bcd237a5299e391af6639657eee97" } } ], "extra": [ 1, 64, 153, 53, 233, 170, 190, 192, 180, 182, 232, 141, 79, 197, 71, 84, 116, 225, 212, 176, 63, 185, 246, 33, 100, 73, 235, 212, 116, 61, 126, 113, 224, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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