Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 109a4b5802a63005a2a194546eb133b0039f1f4540bd64a1685fcbd783745f75

Tx prefix hash: e3d6e191ecf7d20cf242873592ea85d4b87478b30ef8663b85a6e66f5d6d00ba
Tx public key: 28f5f1102d3f70e1ec3cc831d49a676bcfd3db4f1e005c8cd060848262f8f5b2
Timestamp: 1710826520 Timestamp [UCT]: 2024-03-19 05:35:20 Age [y:d:h:m:s]: 01:004:04:21:59
Block: 981521 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263954 RingCT/type: yes/0
Extra: 0128f5f1102d3f70e1ec3cc831d49a676bcfd3db4f1e005c8cd060848262f8f5b202110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f81c98befe1f584bca01457f480378593a481ca54db523a704834a3a5630ee7 0.600000000000 1441618 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": 981531, "vin": [ { "gen": { "height": 981521 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f81c98befe1f584bca01457f480378593a481ca54db523a704834a3a5630ee7" } } ], "extra": [ 1, 40, 245, 241, 16, 45, 63, 112, 225, 236, 60, 200, 49, 212, 154, 103, 107, 207, 211, 219, 79, 30, 0, 92, 140, 208, 96, 132, 130, 98, 248, 245, 178, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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