Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 864a30fc5bb27eab781d75fdee53dffe3c8b73eb0ad8016aa5086013b7fc5c29

Tx prefix hash: 840b1a6e146e9b6aea198f0710a702f31a47ffeacf3e7661b7365ac5e1340b02
Tx public key: 91317a036f84bf97f80838b746d4e05ce185103fa60bfdff11b0df765d622044
Timestamp: 1702688863 Timestamp [UCT]: 2023-12-16 01:07:43 Age [y:d:h:m:s]: 01:183:00:07:58
Block: 914035 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391876 RingCT/type: yes/0
Extra: 0191317a036f84bf97f80838b746d4e05ce185103fa60bfdff11b0df765d622044021100000005faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe1f7b118d2e2ec5389cccdd7c7061561a3b2f5c6f7929861d6bf2b3f48c2705 0.600000000000 1371317 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": 914045, "vin": [ { "gen": { "height": 914035 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe1f7b118d2e2ec5389cccdd7c7061561a3b2f5c6f7929861d6bf2b3f48c2705" } } ], "extra": [ 1, 145, 49, 122, 3, 111, 132, 191, 151, 248, 8, 56, 183, 70, 212, 224, 92, 225, 133, 16, 63, 166, 11, 253, 255, 17, 176, 223, 118, 93, 98, 32, 68, 2, 17, 0, 0, 0, 5, 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