Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff61de3116ae9eeede0e51d230feeb8d6ec34cd50ddc66012808a6d6efc48ab7

Tx prefix hash: a823d7466e5c46d5c3ab2794a5f2767d25148c0207d73d72db2f66090d00a1ef
Tx public key: 0e8e7e51a4753501ca1dd9c046679208652ffebefc7ffa7767552c5d3f0ef287
Timestamp: 1719526135 Timestamp [UCT]: 2024-06-27 22:08:55 Age [y:d:h:m:s]: 00:293:07:54:58
Block: 1053625 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209608 RingCT/type: yes/0
Extra: 010e8e7e51a4753501ca1dd9c046679208652ffebefc7ffa7767552c5d3f0ef2870211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4ffffa5d7e42f4c0a98547a0a4b56b9a713190e1137bf7c4b09e756d07f84d1 0.600000000000 1523972 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": 1053635, "vin": [ { "gen": { "height": 1053625 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4ffffa5d7e42f4c0a98547a0a4b56b9a713190e1137bf7c4b09e756d07f84d1" } } ], "extra": [ 1, 14, 142, 126, 81, 164, 117, 53, 1, 202, 29, 217, 192, 70, 103, 146, 8, 101, 47, 254, 190, 252, 127, 250, 119, 103, 85, 44, 93, 63, 14, 242, 135, 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