Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f0b8d748921c2347e6f3498beb2247ed350133fa72f772d37defbaf16866a57

Tx prefix hash: dd24f987f496d2e0f9cf0fcedb89bf0862aea74fbb0165fa8641de8f6eb7393c
Tx public key: 8c37b1ae184bf3c70a5ab51fe82dff283dcbdac581725bd8aa96da25a6bcaa6d
Timestamp: 1682951352 Timestamp [UCT]: 2023-05-01 14:29:12 Age [y:d:h:m:s]: 01:208:06:57:34
Block: 750651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 410300 RingCT/type: yes/0
Extra: 018c37b1ae184bf3c70a5ab51fe82dff283dcbdac581725bd8aa96da25a6bcaa6d0211000000017e406890000000000000000000

1 output(s) for total of 1.998857477000 dcy

stealth address amount amount idx
00: 689d56308dadf4dd66a57f2cef3f0583b24324e4b204431fc5ab195fee337135 1.998857477000 1198744 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": 750661, "vin": [ { "gen": { "height": 750651 } } ], "vout": [ { "amount": 1998857477, "target": { "key": "689d56308dadf4dd66a57f2cef3f0583b24324e4b204431fc5ab195fee337135" } } ], "extra": [ 1, 140, 55, 177, 174, 24, 75, 243, 199, 10, 90, 181, 31, 232, 45, 255, 40, 61, 203, 218, 197, 129, 114, 91, 216, 170, 150, 218, 37, 166, 188, 170, 109, 2, 17, 0, 0, 0, 1, 126, 64, 104, 144, 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