Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a484f4d741646e40683a624753401534f783848efa8c75a391f4555249fc1bfc

Tx prefix hash: 9100605a9c91ffa45331f1187bc39e385a4d9ac33ebc2b864a3b00a6b81bc923
Tx public key: 8e8d40e8a055f204f8e0f3ea49a06947f05fec3a846a54c49b563acd4ab9bef8
Timestamp: 1707044896 Timestamp [UCT]: 2024-02-04 11:08:16 Age [y:d:h:m:s]: 01:025:08:48:43
Block: 950138 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279167 RingCT/type: yes/0
Extra: 018e8d40e8a055f204f8e0f3ea49a06947f05fec3a846a54c49b563acd4ab9bef80211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f98d1bb09224befd983bf8bf921974c79d6c51bbaa59a01f4720f491216efd2d 0.600000000000 1408700 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": 950148, "vin": [ { "gen": { "height": 950138 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f98d1bb09224befd983bf8bf921974c79d6c51bbaa59a01f4720f491216efd2d" } } ], "extra": [ 1, 142, 141, 64, 232, 160, 85, 242, 4, 248, 224, 243, 234, 73, 160, 105, 71, 240, 95, 236, 58, 132, 106, 84, 196, 155, 86, 58, 205, 74, 185, 190, 248, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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