Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a6f0554210402759a4787146ace11b61c6d35c20ee127d26783ce8ec4919ace

Tx prefix hash: 004bcb1a6185798a2305530403a0e5a1ecddf0224218e8910abbd5428c06849f
Tx public key: a033ee879e0d9b2a7d864dbe85b72ea368c6f0d0400a9f23d9553bb793b909e9
Timestamp: 1717174029 Timestamp [UCT]: 2024-05-31 16:47:09 Age [y:d:h:m:s]: 01:160:18:17:02
Block: 1034129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373468 RingCT/type: yes/0
Extra: 01a033ee879e0d9b2a7d864dbe85b72ea368c6f0d0400a9f23d9553bb793b909e90211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c4e41b8b1376e0f118344341a1dc33aa7ce69ad52bc6584387e080ab5c3a469 0.600000000000 1502608 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": 1034139, "vin": [ { "gen": { "height": 1034129 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c4e41b8b1376e0f118344341a1dc33aa7ce69ad52bc6584387e080ab5c3a469" } } ], "extra": [ 1, 160, 51, 238, 135, 158, 13, 155, 42, 125, 134, 77, 190, 133, 183, 46, 163, 104, 198, 240, 208, 64, 10, 159, 35, 217, 85, 59, 183, 147, 185, 9, 233, 2, 17, 0, 0, 0, 1, 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