Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b40b13ab6c035ad539ecd730fca56397b927743945be0f6d812974d9b0853033

Tx prefix hash: 764679dfa97d77158d59344d3fdfeb7b29f2d31c1d5aee250893915d3204f67e
Tx public key: ea667c68b6e84ee5d2e52a0efaf4f4c62cf29b8e2e4244a60f200d9add13b0ca
Timestamp: 1681459977 Timestamp [UCT]: 2023-04-14 08:12:57 Age [y:d:h:m:s]: 01:354:00:54:08
Block: 738278 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 514306 RingCT/type: yes/0
Extra: 01ea667c68b6e84ee5d2e52a0efaf4f4c62cf29b8e2e4244a60f200d9add13b0ca021100000001faf35c9c000000000000000000

1 output(s) for total of 2.196740377000 dcy

stealth address amount amount idx
00: be8dbfa309f8779ac3e0258e2af7e7a6853ac8bcb8236d474d6a9a7410e54bb7 2.196740377000 1184951 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": 738288, "vin": [ { "gen": { "height": 738278 } } ], "vout": [ { "amount": 2196740377, "target": { "key": "be8dbfa309f8779ac3e0258e2af7e7a6853ac8bcb8236d474d6a9a7410e54bb7" } } ], "extra": [ 1, 234, 102, 124, 104, 182, 232, 78, 229, 210, 229, 42, 14, 250, 244, 244, 198, 44, 242, 155, 142, 46, 66, 68, 166, 15, 32, 13, 154, 221, 19, 176, 202, 2, 17, 0, 0, 0, 1, 250, 243, 92, 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