Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9fbbb1410d0815642c21c061f4dce5d40082fcb5b7d6d5939b9437c865110a0b

Tx prefix hash: 70dd159c5251148c39e0916b9fd9bddc47546117a922f86d219348ce9b88dbbf
Tx public key: 6fa1ca66ac901c62d9f0b73a9f72e6f8dfc7925361110e3bba0ee4069782640b
Timestamp: 1628640952 Timestamp [UCT]: 2021-08-11 00:15:52 Age [y:d:h:m:s]: 03:275:15:21:52
Block: 311428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 969966 RingCT/type: yes/0
Extra: 016fa1ca66ac901c62d9f0b73a9f72e6f8dfc7925361110e3bba0ee4069782640b02110000000fb75ebe6a000000000000000000

1 output(s) for total of 57.034400608000 dcy

stealth address amount amount idx
00: b39ae0a7af931dcfe99b23823232b5f76836fbfd5401107d0e2d317f34cc9ff9 57.034400608000 648147 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": 311438, "vin": [ { "gen": { "height": 311428 } } ], "vout": [ { "amount": 57034400608, "target": { "key": "b39ae0a7af931dcfe99b23823232b5f76836fbfd5401107d0e2d317f34cc9ff9" } } ], "extra": [ 1, 111, 161, 202, 102, 172, 144, 28, 98, 217, 240, 183, 58, 159, 114, 230, 248, 223, 199, 146, 83, 97, 17, 14, 59, 186, 14, 228, 6, 151, 130, 100, 11, 2, 17, 0, 0, 0, 15, 183, 94, 190, 106, 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