Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 846c098a00ec9e8d7107c67a986afa79fc6a19c9de46e91c959fd58428145848

Tx prefix hash: 34728bb376ddbfb7872a6216b3259b1655564c456185b7010c81a5c4b4e723ec
Tx public key: 6b33c87cbaf76e1f897ba8032c5eddeac6251c53bf7b778388d23114d52fd794
Timestamp: 1729444052 Timestamp [UCT]: 2024-10-20 17:07:32 Age [y:d:h:m:s]: 00:081:11:01:37
Block: 1135844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58213 RingCT/type: yes/0
Extra: 016b33c87cbaf76e1f897ba8032c5eddeac6251c53bf7b778388d23114d52fd7940211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19ae5e2a0b171913033ffaae346b29cb0c116aa34884f69d8f89b631c37ae7e8 0.600000000000 1619183 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": 1135854, "vin": [ { "gen": { "height": 1135844 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19ae5e2a0b171913033ffaae346b29cb0c116aa34884f69d8f89b631c37ae7e8" } } ], "extra": [ 1, 107, 51, 200, 124, 186, 247, 110, 31, 137, 123, 168, 3, 44, 94, 221, 234, 198, 37, 28, 83, 191, 123, 119, 131, 136, 210, 49, 20, 213, 47, 215, 148, 2, 17, 0, 0, 0, 3, 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