Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29cc83175449ac48b45ecbd849717a421a1178b99c07e0562a51b9a6a9905402

Tx prefix hash: f82e0d20d500d94ec93e0c17b193e293d1dc6e01febda77ee2a4c35c864235cb
Tx public key: b786c9ccc13e5fe265fa54105784ae1bbe873c7fee92e22288b9aa72ac2803da
Timestamp: 1701158519 Timestamp [UCT]: 2023-11-28 08:01:59 Age [y:d:h:m:s]: 01:142:09:23:45
Block: 901347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362943 RingCT/type: yes/0
Extra: 01b786c9ccc13e5fe265fa54105784ae1bbe873c7fee92e22288b9aa72ac2803da02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.633086720000 dcy

stealth address amount amount idx
00: 93f95d85b553b7587f76e699efe5b27e4f55117dda731b9f4a19e77773a0c3ed 0.633086720000 1357900 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": 901357, "vin": [ { "gen": { "height": 901347 } } ], "vout": [ { "amount": 633086720, "target": { "key": "93f95d85b553b7587f76e699efe5b27e4f55117dda731b9f4a19e77773a0c3ed" } } ], "extra": [ 1, 183, 134, 201, 204, 193, 62, 95, 226, 101, 250, 84, 16, 87, 132, 174, 27, 190, 135, 60, 127, 238, 146, 226, 34, 136, 185, 170, 114, 172, 40, 3, 218, 2, 17, 0, 0, 0, 4, 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