Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d046d9f87c66a0c76f7a38c1252d0d89f7a48990caba78177a2d42359286f31

Tx prefix hash: 662d2e257716c67350531dfe77787ac35b86f14eeff6252769db442ee2b51b3a
Tx public key: 194fe47a56db6da3d3891e5a087388da3f03cc37ba1910bb562d0a537fb6a4b1
Timestamp: 1707501851 Timestamp [UCT]: 2024-02-09 18:04:11 Age [y:d:h:m:s]: 01:276:20:37:08
Block: 953928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 456653 RingCT/type: yes/0
Extra: 01194fe47a56db6da3d3891e5a087388da3f03cc37ba1910bb562d0a537fb6a4b102110000000d7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0591f2ef68da7042543e74d086c1c2684b11947b0500d56a51b7234187e1059f 0.600000000000 1413200 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": 953938, "vin": [ { "gen": { "height": 953928 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0591f2ef68da7042543e74d086c1c2684b11947b0500d56a51b7234187e1059f" } } ], "extra": [ 1, 25, 79, 228, 122, 86, 219, 109, 163, 211, 137, 30, 90, 8, 115, 136, 218, 63, 3, 204, 55, 186, 25, 16, 187, 86, 45, 10, 83, 127, 182, 164, 177, 2, 17, 0, 0, 0, 13, 122, 156, 244, 199, 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