Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 562af88168c921079b43f488e1544d1a779cc8d646c578157aec340fd166ddd5

Tx prefix hash: 47727c74e512c43d96ba0f8e1b9ffabfac0d958a87cb1cb1f3e74efbf65a8621
Tx public key: 7c7c505887accf9100ac42d69fd3d22b12914ec68e0fef496561eae373270e35
Timestamp: 1633154421 Timestamp [UCT]: 2021-10-02 06:00:21 Age [y:d:h:m:s]: 03:037:16:13:45
Block: 344977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 803835 RingCT/type: yes/0
Extra: 017c7c505887accf9100ac42d69fd3d22b12914ec68e0fef496561eae373270e3502110000000f5410958b000000000000000000

1 output(s) for total of 44.151800598000 dcy

stealth address amount amount idx
00: f79b8f3d7d68eb700c2eabf573cd1a1696bc510b237cd3cb151aca217a1839b7 44.151800598000 707701 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": 344987, "vin": [ { "gen": { "height": 344977 } } ], "vout": [ { "amount": 44151800598, "target": { "key": "f79b8f3d7d68eb700c2eabf573cd1a1696bc510b237cd3cb151aca217a1839b7" } } ], "extra": [ 1, 124, 124, 80, 88, 135, 172, 207, 145, 0, 172, 66, 214, 159, 211, 210, 43, 18, 145, 78, 198, 142, 15, 239, 73, 101, 97, 234, 227, 115, 39, 14, 53, 2, 17, 0, 0, 0, 15, 84, 16, 149, 139, 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