Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c656ffd07601d4bd7bac8ba7bfa3c11c775c2b137eea39aeb0c41f480c50409d

Tx prefix hash: 633e5d5a9aae77f665ebc7982a0c1a3a94e47ffa76058436227d1dbcae3dec42
Tx public key: bee8104fc8c4981728c59c6c11fd72ae9d128f6c108cf52534882083aa23df1a
Timestamp: 1739585094 Timestamp [UCT]: 2025-02-15 02:04:54 Age [y:d:h:m:s]: 00:311:00:29:35
Block: 1219516 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220061 RingCT/type: yes/0
Extra: 01bee8104fc8c4981728c59c6c11fd72ae9d128f6c108cf52534882083aa23df1a02110000000f8377ed96000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0028941bf1a0463f56e3c76917ef8f7f3e5a912d047dda39f1acd9b7378b0fa4 0.600000000000 1706341 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": 1219526, "vin": [ { "gen": { "height": 1219516 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0028941bf1a0463f56e3c76917ef8f7f3e5a912d047dda39f1acd9b7378b0fa4" } } ], "extra": [ 1, 190, 232, 16, 79, 200, 196, 152, 23, 40, 197, 156, 108, 17, 253, 114, 174, 157, 18, 143, 108, 16, 140, 245, 37, 52, 136, 32, 131, 170, 35, 223, 26, 2, 17, 0, 0, 0, 15, 131, 119, 237, 150, 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