Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4e88b7877dd5c63ce4fe61199cfd6dc32ce038a175d910060c88822024b1ff9

Tx prefix hash: c08e7633536dc7b997c640e49e00a0bf05931fd99be8be8cb3c28b7bb000f8ac
Tx public key: c283d8347099c0463aa76793a548eb45788f3d4e189dd18d5343b05eb705e064
Timestamp: 1577746266 Timestamp [UCT]: 2019-12-30 22:51:06 Age [y:d:h:m:s]: 04:334:23:19:41
Block: 35363 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1128472 RingCT/type: yes/0
Extra: 01c283d8347099c0463aa76793a548eb45788f3d4e189dd18d5343b05eb705e06402110000010dc3a1a09f000000000000000000

1 output(s) for total of 468.641077349000 dcy

stealth address amount amount idx
00: 5a2206b3d962be4421d02e6c074514efe16d7d6694f6e031ab3185d97d54d4f8 468.641077349000 59587 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": 35373, "vin": [ { "gen": { "height": 35363 } } ], "vout": [ { "amount": 468641077349, "target": { "key": "5a2206b3d962be4421d02e6c074514efe16d7d6694f6e031ab3185d97d54d4f8" } } ], "extra": [ 1, 194, 131, 216, 52, 112, 153, 192, 70, 58, 167, 103, 147, 165, 72, 235, 69, 120, 143, 61, 78, 24, 157, 209, 141, 83, 67, 176, 94, 183, 5, 224, 100, 2, 17, 0, 0, 1, 13, 195, 161, 160, 159, 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