Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 361f1e119c4bd3dc0c2a42f9caff780693fbd95a1cef3082b052a1ff210130cc

Tx prefix hash: 706c7d05befcd20bf05261641e167c7a61ffbc0cad6882111148b6b42581c714
Tx public key: dc561f0f1b96479d796b05277d9879b810a7b898d380db5b91d35c7c16bd81f1
Timestamp: 1732309663 Timestamp [UCT]: 2024-11-22 21:07:43 Age [y:d:h:m:s]: 00:001:06:17:51
Block: 1159504 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 914 RingCT/type: yes/0
Extra: 01dc561f0f1b96479d796b05277d9879b810a7b898d380db5b91d35c7c16bd81f1021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e169c2e2a9fd2a1487bb7379d3630b97ed60443073b7cb2696e838ff31a290f0 0.600000000000 1645141 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": 1159514, "vin": [ { "gen": { "height": 1159504 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e169c2e2a9fd2a1487bb7379d3630b97ed60443073b7cb2696e838ff31a290f0" } } ], "extra": [ 1, 220, 86, 31, 15, 27, 150, 71, 157, 121, 107, 5, 39, 125, 152, 121, 184, 16, 167, 184, 152, 211, 128, 219, 91, 145, 211, 92, 124, 22, 189, 129, 241, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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