Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f74fa6687cc8716acb4c3f93f7d5d27aaa9e6d0748ea46c5805a41530c9b601

Tx prefix hash: 34ddd0c4673ba95b7e86fc2a96675be4a093584eac0e53d7485cb583d5700a2e
Tx public key: 1dbc137dc47961b88df850da47210f6a48e2518149d158cb1a8734b5884a38ba
Timestamp: 1673986308 Timestamp [UCT]: 2023-01-17 20:11:48 Age [y:d:h:m:s]: 02:116:04:59:01
Block: 676940 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 604742 RingCT/type: yes/0
Extra: 011dbc137dc47961b88df850da47210f6a48e2518149d158cb1a8734b5884a38ba0211000000028b7b6602000000000000000000

1 output(s) for total of 3.507653746000 dcy

stealth address amount amount idx
00: 2a635a16d26cff4f3b66f392595286c4c926488c678fad311e72d921c2302e1c 3.507653746000 1118695 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": 676950, "vin": [ { "gen": { "height": 676940 } } ], "vout": [ { "amount": 3507653746, "target": { "key": "2a635a16d26cff4f3b66f392595286c4c926488c678fad311e72d921c2302e1c" } } ], "extra": [ 1, 29, 188, 19, 125, 196, 121, 97, 184, 141, 248, 80, 218, 71, 33, 15, 106, 72, 226, 81, 129, 73, 209, 88, 203, 26, 135, 52, 181, 136, 74, 56, 186, 2, 17, 0, 0, 0, 2, 139, 123, 102, 2, 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