Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8763fb1c96cecfdffb92b4d3aa1e7fceebb2215c952a1c5a4f34b7ea0d724861

Tx prefix hash: 9d06c9311fe9fcc52b1bf177544a31dfc4b8e26cde897984c87523d665520a14
Tx public key: e35a8511d811d1c5f27290d1f42ad861db2ea795f8d54c250681f4b2e31be38f
Timestamp: 1733769677 Timestamp [UCT]: 2024-12-09 18:41:17 Age [y:d:h:m:s]: 00:138:07:30:48
Block: 1171615 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98656 RingCT/type: yes/0
Extra: 01e35a8511d811d1c5f27290d1f42ad861db2ea795f8d54c250681f4b2e31be38f021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4c4c18b063320bca20b4fc0a5fa5e7c64ba6c0322740af7a868ffdc2373f9e6 0.600000000000 1657394 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": 1171625, "vin": [ { "gen": { "height": 1171615 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4c4c18b063320bca20b4fc0a5fa5e7c64ba6c0322740af7a868ffdc2373f9e6" } } ], "extra": [ 1, 227, 90, 133, 17, 216, 17, 209, 197, 242, 114, 144, 209, 244, 42, 216, 97, 219, 46, 167, 149, 248, 213, 76, 37, 6, 129, 244, 178, 227, 27, 227, 143, 2, 17, 0, 0, 0, 3, 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