Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5cb9c9d301a33e9294891c2428a550670e7a6bde550694fa6c8f4c6fc4799eef

Tx prefix hash: e974aef1362bc5643c52358b186481e09f2a40be45f970456c6acdd9bbfd2cb6
Tx public key: 428d203f1a51bef510f15a3a90110fe94432275c402adea209774040d9656438
Timestamp: 1706788399 Timestamp [UCT]: 2024-02-01 11:53:19 Age [y:d:h:m:s]: 01:129:12:39:15
Block: 948008 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353692 RingCT/type: yes/0
Extra: 01428d203f1a51bef510f15a3a90110fe94432275c402adea209774040d96564380211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a3daea5ed6fa8d03bc2f90e172cfa5b2de0f909a63670bac54a6fe45a34d4aa 0.600000000000 1406378 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": 948018, "vin": [ { "gen": { "height": 948008 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a3daea5ed6fa8d03bc2f90e172cfa5b2de0f909a63670bac54a6fe45a34d4aa" } } ], "extra": [ 1, 66, 141, 32, 63, 26, 81, 190, 245, 16, 241, 90, 58, 144, 17, 15, 233, 68, 50, 39, 92, 64, 42, 222, 162, 9, 119, 64, 64, 217, 101, 100, 56, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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