Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8dec7014fe12d6a14c293969e0b9b049d420a7533473eb15815ac64eb49a16c5

Tx prefix hash: b52689b25a554d0bb2588402e087339b30051f0f5440b28badedc9b8aaff57a4
Tx public key: 3a718629de68f617d0d52d26e1109b5ae749893a9961f01662630519401dcb81
Timestamp: 1701902967 Timestamp [UCT]: 2023-12-06 22:49:27 Age [y:d:h:m:s]: 01:107:01:48:39
Block: 907522 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337667 RingCT/type: yes/0
Extra: 013a718629de68f617d0d52d26e1109b5ae749893a9961f01662630519401dcb81021100000005faf35c9c000000000000000000

1 output(s) for total of 0.603952601000 dcy

stealth address amount amount idx
00: c4a02787c8f2962205ba0fd8a98d2d1d1123ee4fa3b20ec4bbd7faa2fedf2e40 0.603952601000 1364515 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": 907532, "vin": [ { "gen": { "height": 907522 } } ], "vout": [ { "amount": 603952601, "target": { "key": "c4a02787c8f2962205ba0fd8a98d2d1d1123ee4fa3b20ec4bbd7faa2fedf2e40" } } ], "extra": [ 1, 58, 113, 134, 41, 222, 104, 246, 23, 208, 213, 45, 38, 225, 16, 155, 90, 231, 73, 137, 58, 153, 97, 240, 22, 98, 99, 5, 25, 64, 29, 203, 129, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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