Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd82f8723b9cddc3c32f61d816b2bfb55dcdf4ffab967ddbb9cc2294f4e1bfac

Tx prefix hash: 6b7bcc7eb6a4f16006565b90d92291a416627efd6f9555bdbae36fb4b374108d
Tx public key: 0486a7011a5facbd57c62166c90e6ace26b396fc7f9f20cb84acf2e0b6981c79
Timestamp: 1736675318 Timestamp [UCT]: 2025-01-12 09:48:38 Age [y:d:h:m:s]: 00:157:22:33:24
Block: 1195658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112569 RingCT/type: yes/0
Extra: 010486a7011a5facbd57c62166c90e6ace26b396fc7f9f20cb84acf2e0b6981c790211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 901611f75900e9a618cb15020a32c3fc08a18eb82de83ddc263bcc6f6890cb20 0.600000000000 1682249 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": 1195668, "vin": [ { "gen": { "height": 1195658 } } ], "vout": [ { "amount": 600000000, "target": { "key": "901611f75900e9a618cb15020a32c3fc08a18eb82de83ddc263bcc6f6890cb20" } } ], "extra": [ 1, 4, 134, 167, 1, 26, 95, 172, 189, 87, 198, 33, 102, 201, 14, 106, 206, 38, 179, 150, 252, 127, 159, 32, 203, 132, 172, 242, 224, 182, 152, 28, 121, 2, 17, 0, 0, 0, 1, 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