Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ba84cb86ae200517a30279ccd27b0359cbcf96e8c28eca53e9b7c72cd9bbb74

Tx prefix hash: e3807b2220f13d942c2ddc052a75ddbb58634cd91ffac739ed90fe095b0b70db
Tx public key: 4f89d4cdcb36e7ea7b2c5011664d0c1c0336fcb6b2bb74078ceffe00ffe8abe2
Timestamp: 1720854664 Timestamp [UCT]: 2024-07-13 07:11:04 Age [y:d:h:m:s]: 00:270:22:39:56
Block: 1064655 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193559 RingCT/type: yes/0
Extra: 014f89d4cdcb36e7ea7b2c5011664d0c1c0336fcb6b2bb74078ceffe00ffe8abe202110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b27d8cbf7e5d4a365b4b5709ff5b87b22e1eb1ed84458f19f420ecc223f5024 0.600000000000 1535186 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": 1064665, "vin": [ { "gen": { "height": 1064655 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b27d8cbf7e5d4a365b4b5709ff5b87b22e1eb1ed84458f19f420ecc223f5024" } } ], "extra": [ 1, 79, 137, 212, 205, 203, 54, 231, 234, 123, 44, 80, 17, 102, 77, 12, 28, 3, 54, 252, 182, 178, 187, 116, 7, 140, 239, 254, 0, 255, 232, 171, 226, 2, 17, 0, 0, 0, 10, 145, 225, 60, 4, 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