Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7b98ffa7a71fbcfc7532ce256f45822aa3b2b2e4028cfdf1559db91c7b8495f

Tx prefix hash: 2aa2e51a356353d1e5b804d012e4ccec568f4c3ad70be8a4e3ebf1e0cac2d8f4
Tx public key: 5667d78da076dd6655bb2c0e89f178a7fe6a1dceaefcead0dc2f1fe27bed0cc2
Timestamp: 1632373794 Timestamp [UCT]: 2021-09-23 05:09:54 Age [y:d:h:m:s]: 03:168:11:49:36
Block: 339246 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 896428 RingCT/type: yes/0
Extra: 015667d78da076dd6655bb2c0e89f178a7fe6a1dceaefcead0dc2f1fe27bed0cc20211000000155d7cc334000000000000000000

1 output(s) for total of 46.125130461000 dcy

stealth address amount amount idx
00: 35306c8dbbd8e4e8d18ea55a3f9333e89a7206bf2ed5be796288ab0a619ea4bb 46.125130461000 697795 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": 339256, "vin": [ { "gen": { "height": 339246 } } ], "vout": [ { "amount": 46125130461, "target": { "key": "35306c8dbbd8e4e8d18ea55a3f9333e89a7206bf2ed5be796288ab0a619ea4bb" } } ], "extra": [ 1, 86, 103, 215, 141, 160, 118, 221, 102, 85, 187, 44, 14, 137, 241, 120, 167, 254, 106, 29, 206, 174, 252, 234, 208, 220, 47, 31, 226, 123, 237, 12, 194, 2, 17, 0, 0, 0, 21, 93, 124, 195, 52, 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