Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f66b1d20a872db296c17f142ff2bb210475faa31d389ebe0c4e5e22c0f29fa1b

Tx prefix hash: 8012fa477c8a08bbaea7cfbbcfdd77a7beac72f2f13da9e2f45e105db572bc57
Tx public key: dc65fab84b0016a983505384faccef4ddcaf19e834e845d62aa2c27489c035f5
Timestamp: 1699382655 Timestamp [UCT]: 2023-11-07 18:44:15 Age [y:d:h:m:s]: 01:046:09:50:28
Block: 886634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294597 RingCT/type: yes/0
Extra: 01dc65fab84b0016a983505384faccef4ddcaf19e834e845d62aa2c27489c035f502110000000175e3f0e9000000000000000000

1 output(s) for total of 0.708293900000 dcy

stealth address amount amount idx
00: d66d4691de689987b537fa75d02f0aefe35dd0f3b0cf91f85b61477a1acc0b8d 0.708293900000 1342463 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": 886644, "vin": [ { "gen": { "height": 886634 } } ], "vout": [ { "amount": 708293900, "target": { "key": "d66d4691de689987b537fa75d02f0aefe35dd0f3b0cf91f85b61477a1acc0b8d" } } ], "extra": [ 1, 220, 101, 250, 184, 75, 0, 22, 169, 131, 80, 83, 132, 250, 204, 239, 77, 220, 175, 25, 232, 52, 232, 69, 214, 42, 162, 194, 116, 137, 192, 53, 245, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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