Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa64eac5f5b7f109d291c0961064eb2b604a17f5830e0193a44bbc393110e41d

Tx prefix hash: 960efef58875a58ddfd071d85693a1451bcadf88f8c8631fa35c1a07bb51306e
Tx public key: 154c74687c61886a7acb4972df583b16985930cec784267af0a8304a9b1dbf82
Timestamp: 1699029924 Timestamp [UCT]: 2023-11-03 16:45:24 Age [y:d:h:m:s]: 01:224:18:34:54
Block: 883911 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 421589 RingCT/type: yes/0
Extra: 01154c74687c61886a7acb4972df583b16985930cec784267af0a8304a9b1dbf8202110000000775e3f0e9000000000000000000

1 output(s) for total of 0.723162563000 dcy

stealth address amount amount idx
00: beb2e605c627d3b47e1ce8fa01ec663f99e90866315e981e526b7ba148ca5c5a 0.723162563000 1339636 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": 883921, "vin": [ { "gen": { "height": 883911 } } ], "vout": [ { "amount": 723162563, "target": { "key": "beb2e605c627d3b47e1ce8fa01ec663f99e90866315e981e526b7ba148ca5c5a" } } ], "extra": [ 1, 21, 76, 116, 104, 124, 97, 136, 106, 122, 203, 73, 114, 223, 88, 59, 22, 152, 89, 48, 206, 199, 132, 38, 122, 240, 168, 48, 74, 155, 29, 191, 130, 2, 17, 0, 0, 0, 7, 117, 227, 240, 233, 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