Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c1a1f406d35a6b5b65f3f43d6c98e341ba02ca56c146c4feeba52e90c4a2b57

Tx prefix hash: ac6913b4081839284b6999ba0c50df23fcadbd9254ce9798a7b9cc21a5cdd110
Tx public key: 582a209dae1945bf93c6c748a00939686eab850906fad89d6b88f73a3fdce1ad
Timestamp: 1729112867 Timestamp [UCT]: 2024-10-16 21:07:47 Age [y:d:h:m:s]: 00:038:09:47:07
Block: 1133108 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27409 RingCT/type: yes/0
Extra: 01582a209dae1945bf93c6c748a00939686eab850906fad89d6b88f73a3fdce1ad02110000000e3cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2edc44670f802bb2af0b5942a00ef09e4df726db2a374f652467e0b110cacdc3 0.600000000000 1616177 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": 1133118, "vin": [ { "gen": { "height": 1133108 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2edc44670f802bb2af0b5942a00ef09e4df726db2a374f652467e0b110cacdc3" } } ], "extra": [ 1, 88, 42, 32, 157, 174, 25, 69, 191, 147, 198, 199, 72, 160, 9, 57, 104, 110, 171, 133, 9, 6, 250, 216, 157, 107, 136, 247, 58, 63, 220, 225, 173, 2, 17, 0, 0, 0, 14, 60, 208, 252, 6, 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