Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90288804268d6d7bb4049e9efdfa9a2011b71f21a2c4f0629af4dbf5d279c644

Tx prefix hash: bb86bf0875614f4f95c0655b56172248c79146c5a6d951c684363851786c9b7d
Tx public key: 96d0a870f2c71b67e1607c2f6bbe34e971861324263b2e4b813864a10b6fe1c3
Timestamp: 1671151733 Timestamp [UCT]: 2022-12-16 00:48:53 Age [y:d:h:m:s]: 02:035:21:09:26
Block: 653472 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 547518 RingCT/type: yes/0
Extra: 0196d0a870f2c71b67e1607c2f6bbe34e971861324263b2e4b813864a10b6fe1c3021100000001e6d27f9c000000000000000000

1 output(s) for total of 4.195425140000 dcy

stealth address amount amount idx
00: d437a8a049980fa40d3ebb6807b326b0ab716cfb19391035a37463b9ecb10248 4.195425140000 1093937 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": 653482, "vin": [ { "gen": { "height": 653472 } } ], "vout": [ { "amount": 4195425140, "target": { "key": "d437a8a049980fa40d3ebb6807b326b0ab716cfb19391035a37463b9ecb10248" } } ], "extra": [ 1, 150, 208, 168, 112, 242, 199, 27, 103, 225, 96, 124, 47, 107, 190, 52, 233, 113, 134, 19, 36, 38, 59, 46, 75, 129, 56, 100, 161, 11, 111, 225, 195, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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