Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b4125aa838ffb40983f6f72d2effc48e88efff4362aac8a7f223733c2c388fe

Tx prefix hash: 4357aea218ee10d4899d3435bdac57d71d8a99314938d75c516852a57e0363cb
Tx public key: 686ce8b7cb449af34fa4e6cce7ba339c98ff671eb3f9503281a936e108a32f1b
Timestamp: 1650350132 Timestamp [UCT]: 2022-04-19 06:35:32 Age [y:d:h:m:s]: 02:294:15:19:51
Block: 483386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 730254 RingCT/type: yes/0
Extra: 01686ce8b7cb449af34fa4e6cce7ba339c98ff671eb3f9503281a936e108a32f1b02110000000bcb8520c2000000000000000000

1 output(s) for total of 15.358250568000 dcy

stealth address amount amount idx
00: dea74e17ee33448f2d1239f53ba4fdc8f8b458ecae14d718ea736dca246a9ad6 15.358250568000 905057 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": 483396, "vin": [ { "gen": { "height": 483386 } } ], "vout": [ { "amount": 15358250568, "target": { "key": "dea74e17ee33448f2d1239f53ba4fdc8f8b458ecae14d718ea736dca246a9ad6" } } ], "extra": [ 1, 104, 108, 232, 183, 203, 68, 154, 243, 79, 164, 230, 204, 231, 186, 51, 156, 152, 255, 103, 30, 179, 249, 80, 50, 129, 169, 54, 225, 8, 163, 47, 27, 2, 17, 0, 0, 0, 11, 203, 133, 32, 194, 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