Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c28a1ef5024e141e2d217b7afdeed724382a0ca9c318026a540dce57957ccd3b

Tx prefix hash: 61108ebb9937416f0349f6a94605f8f3bc0198ebc403dec4b0872aa9d48f9d69
Tx public key: 4c4221cbeacb31a0a61175e134a7c680ef5b611a2237867fc6c18c4f3b4be23d
Timestamp: 1731841792 Timestamp [UCT]: 2024-11-17 11:09:52 Age [y:d:h:m:s]: 00:157:04:31:56
Block: 1155634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112176 RingCT/type: yes/0
Extra: 014c4221cbeacb31a0a61175e134a7c680ef5b611a2237867fc6c18c4f3b4be23d021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe54058072752c919ef181123d24ab4e4e2438e6eae9c103494dae23c05a2f48 0.600000000000 1641251 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": 1155644, "vin": [ { "gen": { "height": 1155634 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe54058072752c919ef181123d24ab4e4e2438e6eae9c103494dae23c05a2f48" } } ], "extra": [ 1, 76, 66, 33, 203, 234, 203, 49, 160, 166, 17, 117, 225, 52, 167, 198, 128, 239, 91, 97, 26, 34, 55, 134, 127, 198, 193, 140, 79, 59, 75, 226, 61, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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