Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7ba7c7c65fa0857624c9004d47967d32312344c21c59c547b25bfb5aa5947a5

Tx prefix hash: b11744ec24c991f81297bfdce3fdd1fd9b5de041c8b98b3eb5a191f9112fe24b
Tx public key: f8565fc0d645283070ddb12ed86d33d7bd44d8d17f11d095d7c1a0de31fc7be8
Timestamp: 1645525945 Timestamp [UCT]: 2022-02-22 10:32:25 Age [y:d:h:m:s]: 03:065:02:15:35
Block: 443989 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 826601 RingCT/type: yes/0
Extra: 01f8565fc0d645283070ddb12ed86d33d7bd44d8d17f11d095d7c1a0de31fc7be802110000000cbf7ee4e7000000000000000000

1 output(s) for total of 20.747452924000 dcy

stealth address amount amount idx
00: b06f3b306d9fd3b4e9b7c98fd0c1f7af0c249a0af2682df2d384607337178175 20.747452924000 857154 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": 443999, "vin": [ { "gen": { "height": 443989 } } ], "vout": [ { "amount": 20747452924, "target": { "key": "b06f3b306d9fd3b4e9b7c98fd0c1f7af0c249a0af2682df2d384607337178175" } } ], "extra": [ 1, 248, 86, 95, 192, 214, 69, 40, 48, 112, 221, 177, 46, 216, 109, 51, 215, 189, 68, 216, 209, 127, 17, 208, 149, 215, 193, 160, 222, 49, 252, 123, 232, 2, 17, 0, 0, 0, 12, 191, 126, 228, 231, 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