Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b985784a98fd48319a20149022c950f40e401a85b9e1a53e0db5542a7a5037ce

Tx prefix hash: 7d83aaab1a7369756b64e9e9cbcc59d48dc9aea8b513131c739d5f316ca3950e
Tx public key: 9f80b50f7f85ec20987204bf66ed5789ef39dcf9e2b40d12461c5a95e59d31c7
Timestamp: 1718948175 Timestamp [UCT]: 2024-06-21 05:36:15 Age [y:d:h:m:s]: 00:292:21:58:19
Block: 1048844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209308 RingCT/type: yes/0
Extra: 019f80b50f7f85ec20987204bf66ed5789ef39dcf9e2b40d12461c5a95e59d31c702110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab3b1ec32bde9b7d14e2e10b71e887da3aab6b27e13e9ddfca01bda6f0330a0e 0.600000000000 1518931 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": 1048854, "vin": [ { "gen": { "height": 1048844 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab3b1ec32bde9b7d14e2e10b71e887da3aab6b27e13e9ddfca01bda6f0330a0e" } } ], "extra": [ 1, 159, 128, 181, 15, 127, 133, 236, 32, 152, 114, 4, 191, 102, 237, 87, 137, 239, 57, 220, 249, 226, 180, 13, 18, 70, 28, 90, 149, 229, 157, 49, 199, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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