Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54f961eb216446ab56de1891d8483d11069cb7b783a2e248bbbd9bd3eccd6eb3

Tx prefix hash: 9f358485b628b4ebcca2e7d7e684f753c3fdfaf030bd4fb3ecd21c98b28bfe43
Tx public key: e5cf6c70523aaf65b8435d2e3f765e42d5daa8fa7709babc265d34ae38ad56c6
Timestamp: 1710657817 Timestamp [UCT]: 2024-03-17 06:43:37 Age [y:d:h:m:s]: 00:287:05:08:42
Block: 980129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205568 RingCT/type: yes/0
Extra: 01e5cf6c70523aaf65b8435d2e3f765e42d5daa8fa7709babc265d34ae38ad56c60211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba508a8d391300d79b8ab175e931c34a58f9fb1fa776118fba41d8b38fd465e3 0.600000000000 1440188 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": 980139, "vin": [ { "gen": { "height": 980129 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba508a8d391300d79b8ab175e931c34a58f9fb1fa776118fba41d8b38fd465e3" } } ], "extra": [ 1, 229, 207, 108, 112, 82, 58, 175, 101, 184, 67, 93, 46, 63, 118, 94, 66, 213, 218, 168, 250, 119, 9, 186, 188, 38, 93, 52, 174, 56, 173, 86, 198, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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