Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a6255478b599dfbccbb782db0a235bbdfade907f003213f050e1e9fc58e4bda

Tx prefix hash: c68881566c90e79d606aea4bdfaf5ba01e0257ff3e3b39b5a27d73bb9d0f7f85
Tx public key: 1f9f7f5541dd37e7b3f76b188d0bd402d1bd385940f04ea7882c29709ad44f90
Timestamp: 1577786083 Timestamp [UCT]: 2019-12-31 09:54:43 Age [y:d:h:m:s]: 05:064:20:43:49
Block: 35601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1196175 RingCT/type: yes/0
Extra: 011f9f7f5541dd37e7b3f76b188d0bd402d1bd385940f04ea7882c29709ad44f900211000000128a2ee0d9000000000000000000

1 output(s) for total of 467.778182771000 dcy

stealth address amount amount idx
00: 4c1f22cd0d002e84eb1a92db339d0f6f3a83bf8708654a87d9bf1a554e4d2113 467.778182771000 60100 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": 35611, "vin": [ { "gen": { "height": 35601 } } ], "vout": [ { "amount": 467778182771, "target": { "key": "4c1f22cd0d002e84eb1a92db339d0f6f3a83bf8708654a87d9bf1a554e4d2113" } } ], "extra": [ 1, 31, 159, 127, 85, 65, 221, 55, 231, 179, 247, 107, 24, 141, 11, 212, 2, 209, 189, 56, 89, 64, 240, 78, 167, 136, 44, 41, 112, 154, 212, 79, 144, 2, 17, 0, 0, 0, 18, 138, 46, 224, 217, 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