Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fbbe4853afb8f41a0bff263853062d00014be9c185f45e901e27436e907d1d99

Tx prefix hash: f2f61f3cc143a788c23e79e0e1f2999e9bd13626a2b0e9bf1f7d70ad4eed4656
Tx public key: 68952a33322f3812303af2d802520ce27ed08c8cbafaa94a5a09926e634d6ad6
Timestamp: 1709102963 Timestamp [UCT]: 2024-02-28 06:49:23 Age [y:d:h:m:s]: 01:055:20:10:04
Block: 967223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300918 RingCT/type: yes/0
Extra: 0168952a33322f3812303af2d802520ce27ed08c8cbafaa94a5a09926e634d6ad60211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d7170d0d582ffc61f8df6a17e6187cafa5dc18c748655a9e5c15f01e227ee69 0.600000000000 1426994 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": 967233, "vin": [ { "gen": { "height": 967223 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d7170d0d582ffc61f8df6a17e6187cafa5dc18c748655a9e5c15f01e227ee69" } } ], "extra": [ 1, 104, 149, 42, 51, 50, 47, 56, 18, 48, 58, 242, 216, 2, 82, 12, 226, 126, 208, 140, 140, 186, 250, 169, 74, 90, 9, 146, 110, 99, 77, 106, 214, 2, 17, 0, 0, 0, 4, 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