Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 468393691bd2418c89d187ae4e36970ca06c306be360fa9142a5de061a602a01

Tx prefix hash: 3589754d9065d7d47647895ce9c3a3b14688cc730f46da9c2a2a897542acde9d
Tx public key: 444ea08364297bf4d8676be90b52b165384f699d035415abd18c17d6b4672ea9
Timestamp: 1690426040 Timestamp [UCT]: 2023-07-27 02:47:20 Age [y:d:h:m:s]: 01:259:02:08:13
Block: 812641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 446271 RingCT/type: yes/0
Extra: 01444ea08364297bf4d8676be90b52b165384f699d035415abd18c17d6b4672ea902110000000275e3f0e9000000000000000000

1 output(s) for total of 1.245613008000 dcy

stealth address amount amount idx
00: 3d2fb61e58c6b2ab8b368c6a986bcf0ed16d5fa0c598cfb87fe358451d1da8aa 1.245613008000 1264348 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": 812651, "vin": [ { "gen": { "height": 812641 } } ], "vout": [ { "amount": 1245613008, "target": { "key": "3d2fb61e58c6b2ab8b368c6a986bcf0ed16d5fa0c598cfb87fe358451d1da8aa" } } ], "extra": [ 1, 68, 78, 160, 131, 100, 41, 123, 244, 216, 103, 107, 233, 11, 82, 177, 101, 56, 79, 105, 157, 3, 84, 21, 171, 209, 140, 23, 214, 180, 103, 46, 169, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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