Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d5784a257e958cfb561ecfa18afdbf2b44d1d30166cab7220912240484d5180

Tx prefix hash: cea5967cb15bca03f4f65f4b9a64f8c2b042d2a7d237a6cabeb56c74e35a79ea
Tx public key: c755ea979dd78f3aa7c34fab450aabc2dbe01f4d7430040e19d01074987d693a
Timestamp: 1708433340 Timestamp [UCT]: 2024-02-20 12:49:00 Age [y:d:h:m:s]: 01:090:21:22:46
Block: 961665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326017 RingCT/type: yes/0
Extra: 01c755ea979dd78f3aa7c34fab450aabc2dbe01f4d7430040e19d01074987d693a0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49e035a7858071a503b2796854f8b0a492f208c1a6491fbfccf63c0e040bf6ee 0.600000000000 1421276 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": 961675, "vin": [ { "gen": { "height": 961665 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49e035a7858071a503b2796854f8b0a492f208c1a6491fbfccf63c0e040bf6ee" } } ], "extra": [ 1, 199, 85, 234, 151, 157, 215, 143, 58, 167, 195, 79, 171, 69, 10, 171, 194, 219, 224, 31, 77, 116, 48, 4, 14, 25, 208, 16, 116, 152, 125, 105, 58, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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