Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da48a248ac8edd6e04c13d2a12e984bb7c0694c6c6c75cd49e8cea779daaf38d

Tx prefix hash: f639bb93c5ec95bfba3896b2a6acc7342780ef411e35b0d53860c63e465f63a7
Tx public key: 436eeb0ee8a39ebeb6bfcb5f92f67f0d7e213f163f59d6278100cb1961d0d194
Timestamp: 1739757982 Timestamp [UCT]: 2025-02-17 02:06:22 Age [y:d:h:m:s]: 00:223:16:50:06
Block: 1220877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157591 RingCT/type: yes/0
Extra: 01436eeb0ee8a39ebeb6bfcb5f92f67f0d7e213f163f59d6278100cb1961d0d194021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44cd077a28beddb14b9af8f6512279b7c442ae2b3b8947562c59f4b0c6347b34 0.600000000000 1707718 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": 1220887, "vin": [ { "gen": { "height": 1220877 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44cd077a28beddb14b9af8f6512279b7c442ae2b3b8947562c59f4b0c6347b34" } } ], "extra": [ 1, 67, 110, 235, 14, 232, 163, 158, 190, 182, 191, 203, 95, 146, 246, 127, 13, 126, 33, 63, 22, 63, 89, 214, 39, 129, 0, 203, 25, 97, 208, 209, 148, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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