Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4128a24b4e5fc1c2ad333da5b1cb929b6b4eb7a49114733e91358be95a37425

Tx prefix hash: 6057176bfaf676b1c81a61558c7b18a2ee3f7fbc9bd590f279d4453e20e32bb8
Tx public key: 012dc2286a1c8233b3d17454221d2a037cde245e48b780ff5ca8c1075a36d305
Timestamp: 1724028164 Timestamp [UCT]: 2024-08-19 00:42:44 Age [y:d:h:m:s]: 00:226:02:19:20
Block: 1090952 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161444 RingCT/type: yes/0
Extra: 01012dc2286a1c8233b3d17454221d2a037cde245e48b780ff5ca8c1075a36d30502110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dcab3a28fa839d448fe31b5b6edb21f01e7403d2f564283a1c66fb962e102770 0.600000000000 1565577 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": 1090962, "vin": [ { "gen": { "height": 1090952 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dcab3a28fa839d448fe31b5b6edb21f01e7403d2f564283a1c66fb962e102770" } } ], "extra": [ 1, 1, 45, 194, 40, 106, 28, 130, 51, 179, 209, 116, 84, 34, 29, 42, 3, 124, 222, 36, 94, 72, 183, 128, 255, 92, 168, 193, 7, 90, 54, 211, 5, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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