Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 949fa02761b8fa038f06012483fc3d9ab11dc5aace4aa6621d7da0561ef72ae1

Tx prefix hash: c513e49a9e804d976764e9cdd355b615cf74f732f14ec09fac1e19ac087117fb
Tx public key: cd67fb35d1fd3c7078067f3d07ee57bff22927c3163ad077de908551b026e1e5
Timestamp: 1734430420 Timestamp [UCT]: 2024-12-17 10:13:40 Age [y:d:h:m:s]: 00:106:06:12:55
Block: 1177103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75707 RingCT/type: yes/0
Extra: 01cd67fb35d1fd3c7078067f3d07ee57bff22927c3163ad077de908551b026e1e50211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e6e99c44fcee283ffd143dbdf52bf7035a82ebc065832a2f55d4234056d00873 0.600000000000 1663466 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": 1177113, "vin": [ { "gen": { "height": 1177103 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e6e99c44fcee283ffd143dbdf52bf7035a82ebc065832a2f55d4234056d00873" } } ], "extra": [ 1, 205, 103, 251, 53, 209, 253, 60, 112, 120, 6, 127, 61, 7, 238, 87, 191, 242, 41, 39, 195, 22, 58, 208, 119, 222, 144, 133, 81, 176, 38, 225, 229, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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