Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ea83925cdb589f2a4a07dd7215dd4a147d1107c96aaa313ea57115521ba0e0e

Tx prefix hash: ab67eb67d83c998b67f44425aa2e2bd28ec5839b738c7188b1b6ed9897ab5e0e
Tx public key: 5f0d23f049329b48be869f3bc41be33a6601fb432a7048e02128432d1dc8a476
Timestamp: 1722771168 Timestamp [UCT]: 2024-08-04 11:32:48 Age [y:d:h:m:s]: 00:202:22:49:41
Block: 1080529 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144909 RingCT/type: yes/0
Extra: 015f0d23f049329b48be869f3bc41be33a6601fb432a7048e02128432d1dc8a476021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ecd6de4d3780f86443cd0b8afbb4d960e2dff3eb4149bc6b7858c2607d1a549 0.600000000000 1553922 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": 1080539, "vin": [ { "gen": { "height": 1080529 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ecd6de4d3780f86443cd0b8afbb4d960e2dff3eb4149bc6b7858c2607d1a549" } } ], "extra": [ 1, 95, 13, 35, 240, 73, 50, 155, 72, 190, 134, 159, 59, 196, 27, 227, 58, 102, 1, 251, 67, 42, 112, 72, 224, 33, 40, 67, 45, 29, 200, 164, 118, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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