Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 196882923103d52f2e12af7d51f7cb6264fc303975df24fcfedca3beebfe55b7

Tx prefix hash: c1c049bee1f6d6eb17f01b1a5f6063f1f0172c5ffc9ee9da133faaf46bd27710
Tx public key: a1075a9dd30ba4ac86542d129b33fab5b7f479fd068a9e05d1f77f5f3d3fdb73
Timestamp: 1699832524 Timestamp [UCT]: 2023-11-12 23:42:04 Age [y:d:h:m:s]: 01:206:09:20:11
Block: 890368 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 408725 RingCT/type: yes/0
Extra: 01a1075a9dd30ba4ac86542d129b33fab5b7f479fd068a9e05d1f77f5f3d3fdb73021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.688400543000 dcy

stealth address amount amount idx
00: 45bc5f85e02efe82399d6d902d871c69ad6ca522fed4876f7093a3d2cf53c93a 0.688400543000 1346391 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": 890378, "vin": [ { "gen": { "height": 890368 } } ], "vout": [ { "amount": 688400543, "target": { "key": "45bc5f85e02efe82399d6d902d871c69ad6ca522fed4876f7093a3d2cf53c93a" } } ], "extra": [ 1, 161, 7, 90, 157, 211, 11, 164, 172, 134, 84, 45, 18, 155, 51, 250, 181, 183, 244, 121, 253, 6, 138, 158, 5, 209, 247, 127, 95, 61, 63, 219, 115, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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