Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4dbb6e5c364b059920b56fec1318cb317db220fd811a34d403e85173592a6c39

Tx prefix hash: 6b79c87df3b24c3780bad3fb13aa99d5d8492ae27743adb7b50839304d9040d2
Tx public key: 595a48c9cd9d86ad651c8ff81f7df7f948333def2dcabcf50397dc584ec067ce
Timestamp: 1725059894 Timestamp [UCT]: 2024-08-30 23:18:14 Age [y:d:h:m:s]: 00:266:14:22:04
Block: 1099500 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190433 RingCT/type: yes/0
Extra: 01595a48c9cd9d86ad651c8ff81f7df7f948333def2dcabcf50397dc584ec067ce021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51b150cd3e67c46959b37c40dba736cffac1bacfcd548cf6a2b92808640bffd2 0.600000000000 1575463 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": 1099510, "vin": [ { "gen": { "height": 1099500 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51b150cd3e67c46959b37c40dba736cffac1bacfcd548cf6a2b92808640bffd2" } } ], "extra": [ 1, 89, 90, 72, 201, 205, 157, 134, 173, 101, 28, 143, 248, 31, 125, 247, 249, 72, 51, 61, 239, 45, 202, 188, 245, 3, 151, 220, 88, 78, 192, 103, 206, 2, 17, 0, 0, 0, 3, 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