Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3cba56aed7dff13230a5e705d80eea293bc639c7b353e49cf549f4547034dc1

Tx prefix hash: 1b558f8afacd24ab2888947e9b8332007fe0693a31ff5cc48d1911847b1a2e32
Tx public key: be56fb7fdc79ee9cc3a6e789c0f1fc5324c2dfdcc1d3007337d8b0c948631e8b
Timestamp: 1694944994 Timestamp [UCT]: 2023-09-17 10:03:14 Age [y:d:h:m:s]: 02:058:10:10:25
Block: 850029 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 561427 RingCT/type: yes/0
Extra: 01be56fb7fdc79ee9cc3a6e789c0f1fc5324c2dfdcc1d3007337d8b0c948631e8b02110000000ce6d27f9c000000000000000000

1 output(s) for total of 0.936485626000 dcy

stealth address amount amount idx
00: 778e064096616f1e1c959add1d93da1345655aa989ae07504f9611df7f23c8e1 0.936485626000 1303723 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": 850039, "vin": [ { "gen": { "height": 850029 } } ], "vout": [ { "amount": 936485626, "target": { "key": "778e064096616f1e1c959add1d93da1345655aa989ae07504f9611df7f23c8e1" } } ], "extra": [ 1, 190, 86, 251, 127, 220, 121, 238, 156, 195, 166, 231, 137, 192, 241, 252, 83, 36, 194, 223, 220, 193, 211, 0, 115, 55, 216, 176, 201, 72, 99, 30, 139, 2, 17, 0, 0, 0, 12, 230, 210, 127, 156, 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