Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 366ee7f210434dc6432c42b4035cf696210cd6428b82d917f558d91b3ce687a9

Tx prefix hash: 4b5ef359796641cda4a3bc3e66eb505c768b7af0960aa2f56f394702e93fd187
Tx public key: 075ea7466bc47999e09d77a63e3a22b0cecfc4a81f87e8a2ec716c1562dbb2d7
Timestamp: 1729797549 Timestamp [UCT]: 2024-10-24 19:19:09 Age [y:d:h:m:s]: 00:030:15:43:20
Block: 1138743 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 21898 RingCT/type: yes/0
Extra: 01075ea7466bc47999e09d77a63e3a22b0cecfc4a81f87e8a2ec716c1562dbb2d70211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d06fec308cdda0d93773a3bdba454f27b8aafbc14ff05324573fd0713cbd281d 0.600000000000 1622456 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": 1138753, "vin": [ { "gen": { "height": 1138743 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d06fec308cdda0d93773a3bdba454f27b8aafbc14ff05324573fd0713cbd281d" } } ], "extra": [ 1, 7, 94, 167, 70, 107, 196, 121, 153, 224, 157, 119, 166, 62, 58, 34, 176, 206, 207, 196, 168, 31, 135, 232, 162, 236, 113, 108, 21, 98, 219, 178, 215, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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