Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43e24dbe2940978cba113982a57c79144d4dfa80f2a7b0da6c66ddeae58eec7c

Tx prefix hash: 5a3a859e2a3526bbcaa672ac5a5dde1918ccc54b80fef6ace1a4f8e1f57b7920
Tx public key: af544baa4e08499bf15ad69c7b775504577b867f0c1f7d396a8066692c8b5ca5
Timestamp: 1732783732 Timestamp [UCT]: 2024-11-28 08:48:52 Age [y:d:h:m:s]: 01:018:21:48:25
Block: 1163442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271947 RingCT/type: yes/0
Extra: 01af544baa4e08499bf15ad69c7b775504577b867f0c1f7d396a8066692c8b5ca50211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31b989f7e72ff73f9de26e7c0a392599302417704d73c4b0216ec85a0adee648 0.600000000000 1649109 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": 1163452, "vin": [ { "gen": { "height": 1163442 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31b989f7e72ff73f9de26e7c0a392599302417704d73c4b0216ec85a0adee648" } } ], "extra": [ 1, 175, 84, 75, 170, 78, 8, 73, 155, 241, 90, 214, 156, 123, 119, 85, 4, 87, 123, 134, 127, 12, 31, 125, 57, 106, 128, 102, 105, 44, 139, 92, 165, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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